Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@liammartens it's a shameless hack indeed 🙃
-
@alkuzad that code will probably never get out of my laptop, so why bother?
-
@spky If I had read your comment 5 hours earlier I wouldn't have gotten the joke. What a coincidence that I just read a random Quora answer about this :).
-
@sm1th This was no joke.. (unfortunately)
Just enjoy over 70 lines of code, someone else would squeeze into 4 lines:
https://gist.github.com/xorrbit/... -
@spky Oh I guess they were talking about an old version of the true command, which was an empty file because empty scripts exits with 0. And AT&T still had their copyright in it...
This is not the article that I first saw (Can't find it) but here's another one explaining the history:
https://quora.com/What-is-the-dumbe... -
@sm1th Ah, ok. I didn't know the story with that copyright notice.
Very weird story, indeed.
Thanks for the link 😀 -
@spky Yeah that's why I thought you were being sarcastic when you said the source code was huge XD
Related Rants
She runs C shells by the seashore.
I wanted that Makefile to avoid stripping binaries after building them, but there was no clear option for that. I only found this:
STRIP = strip
That tells where to find the executable that does the stripping. I changed it to a no-op executable, like "true".
So now I have
STRIP = true
to disable stripping.
undefined
makefile
c
wk19