News for hackers. Stuff that matters.
Re:Magic is often used to describe confusing code by beachstartup on Friday March 25, 2016 @08:57PM (#11363862)
the problem is when you use magic, you're deliberately being clever, and the only proper way to be clever is if you thoroughly document your cleverness with comments and diagrams and examples. the person you befuddle with how clever you are is probably yourself, 2 years from now.
Re:Magic is often used to describe confusing code by SixSigma on Saturday March 26, 2016 @07:50AM (#11365316)
see - Lions' Commentary on UNIX 6th Edition, with Source Code [1]

[1] https://en.wikipedia.org/wiki/Lions%27_Commentary_on_UNIX_6t...

        /*
         * If the new process paused because it was
         * swapped out, set the stack level to the last call
         * to savu(u_ssav).  This means that the return
         * which is executed immediately after the call to aretu
         * actually returns from the last routine which did
         * the savu.
         *
         * You are not expected to understand this.
         */
        if(rp->p_flag&SSWAP) {
                rp->p_flag =& ~SSWAP;
                aretu(u.u_ssav);
        }
Re:Magic is often used to describe confusing code by StavrosK on Friday March 25, 2016 @11:08PM (#11364261)
Eh, try a month.
Re:Magic is often used to describe confusing code by MaulingMonkey on Saturday March 26, 2016 @05:51AM (#11365063)
Later today: Wait, what was I doing again?
Re:Magic is often used to describe confusing code by StavrosK on Saturday March 26, 2016 @07:04AM (#11365226)
What is this in reply to?
Re:Magic is often used to describe confusing code by andrewflnr on Saturday March 26, 2016 @12:22PM (#11366198)
I think they were raising your "try a month" to "try 6 hours".
Re:Magic is often used to describe confusing code by StavrosK on Sunday March 27, 2016 @10:36AM (#11370063)
Yes, and I was re-raising it to "five minutes" :( Apparently the joke wasn't very obvious.
Re:Magic is often used to describe confusing code by MaulingMonkey on Saturday March 26, 2016 @02:31PM (#11366791)
Correct. Thanks!