Re:Avast open-sources its machine-code decompiler
by drej on Wednesday December 13, 2017 @06:54AM
(#15913662)
Now the usual for large projects like this one (this is just for the main repo):
[ Parent
| on HN ]
Re:Avast open-sources its machine-code decompiler
by jwilk on Wednesday December 13, 2017 @07:14AM
(#15913722)
> Now the usual for large projects like this one (this is just for the main repo):
I don't understand what you're trying to say. The usual... what?
Re:Avast open-sources its machine-code decompiler
by drej on Wednesday December 13, 2017 @07:23AM
(#15913763)
Oh, I thought that we do this sort of thing whenever there's a new open source project posted here. People seem to want to know what it's made of and potentially its (S)LOC.
Re:Avast open-sources its machine-code decompiler
by chrisseaton on Wednesday December 13, 2017 @07:41AM
(#15913843)
I've never seen anyone do that on here.
Re:Avast open-sources its machine-code decompiler
by exikyut on Wednesday December 13, 2017 @09:05AM
(#15914233)
But I like it. GitHub is all like "98.6% C++, 1.4% Other", which is... an understandable heuristic, but very meh.
Re:Avast open-sources its machine-code decompiler
by chrisseaton on Wednesday December 13, 2017 @09:21AM
(#15914336)
I wish GitHub let me customise which directories to include. My project shows up as 74% Ruby, but a lot of that is some specs that aren't really part of the project, and in reality it's 60% Ruby.
Re:Avast open-sources its machine-code decompiler
by jwilk on Wednesday December 13, 2017 @12:32PM
(#15915741)
To some extent, you can influence GitHub's classification via gitattributes:
Re:Avast open-sources its machine-code decompiler
by Fnoord on Wednesday December 20, 2017 @12:35PM
(#15971751)
Didn't know about loc or this thing, thanks for bringing it up.
Re:Avast open-sources its machine-code decompiler
by oneweekwonder on Wednesday December 13, 2017 @10:12AM
(#15914685)
I wonder if there is a website/api that will give you loc of pypi or npm packages.
Maybe in the form of a forum badge or certificate like pdf.
Re:Avast open-sources its machine-code decompiler
by slowmotiony on Wednesday December 13, 2017 @07:36AM
(#15913822)
So there are two lines of ASP.NET code? Do I read this correctly?
Re:Avast open-sources its machine-code decompiler
by dspillett on Wednesday December 13, 2017 @08:04AM
(#15913940)
Two single line files that have a file extension making them look like ASP.net code is how I read that.
It could be place-holder scripts that redirect to the correct location, for instance a default.asp/index.asp file that does nothing but redirect to index.html some other default that IIS doesn't recognised out of the box. This would catch cases where someone has just dumped the web assets on a IIS share (IIS doesn't, or at least didn't used to, consider index.html as a potential default document). In classic ASP this would be something like the line:
<% response.redirect "index.whatever-extension" %>
It could also be false positives in whatever test is being performed. For a project like this, I suspect that is more likely to be the case.
Re:Avast open-sources its machine-code decompiler
by bringtheaction on Wednesday December 13, 2017 @07:48AM
(#15913873)
Probably a misclassification. It's not 100% accurate but it gives a good idea of the size and languages of the code base.