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.
I don't understand what you're trying to say. The usual... what?