4 ms·
https://github.com/uutils/coreutils/search?q=gnu https://github.com/uutils/coreutils/search?q=gnu "This is the way it was implemented in GNU split." i dunno may
by moocowtruck 6y ago
https://github.com/uutils/coreutils/search?q=gnu https://github.com/uutils/coreutils/search?q=gnu
"This is the way it was implemented in GNU split."
i dunno maybe there are cases where they copy more than behavior... but interesting to look through
- okl 6y agoThere are more examples, here is one: // a few global constants as used in the GNU implementation
- danudey 6y agoIt's pretty easy to ask someone "Hey, can you go take a look at GNU split and see how they handle this case?" and then implement your own clean-room solution afterwards. Alternately, to solve the problem yourself and mention it to someone and have them say "that's how GNU split does it, so why not?"
- eximius 6y agoIsn't that, by definition, not a clean-room solution?
- moonchild 6y ago‘Clean-room reverse engineering’ refers to the practice of having one person look at disassembled source code, spec sheets, actual behaviour, etc. of some program; describe that behaviour to a second person; and having the second person implement the described behaviour. https://en.wikipedia.org/wiki/Chinese_wall#Reverse_engineering https://en.wikipedia.org/wiki/Chinese_wall#Reverse_engineeri...
- eximius 6y agoAh, that's interesting! I didn't know that was a sufficient insulation of IP.
- moocowtruck 6y agoyea seems pretty easy then right, sounds like no source that is available for eyes to see is safe from 'clean room reverse engineering'