News for hackers. Stuff that matters.
Re:Why did the original code for FIND.COM use lop as a label... by cbd1984 on Thursday April 16, 2015 @08:52PM (#9391697)
But wouldn't the colon at the end disambiguate? It seems like the colon is mandatory for labels and forbidden for opcodes.

(My comment, which got flagged as spam. Is spam-flagging common on that blog, or is it just random?)

Re:Why did the original code for FIND.COM use lop as a label... by virulent on Thursday April 16, 2015 @05:07PM (#9390752)
I enjoyed the linked post[1] at the bottom more than the post itself.

    #define while(x) if(x)
Too bad April 1 is already gone, I'm kind of tempted to try and sneak that in.

[1] http://www.cs.earlham.edu/~skylar/humor/Unix/c.language.pran...

Re:Why did the original code for FIND.COM use lop as a label... by geocar on Thursday April 16, 2015 @04:53PM (#9390681)
Then why is it `lop:` instead of `lop`?

Doesn't the colon mean label?

Re:Why did the original code for FIND.COM use lop as a label... by hermanhermitage on Thursday April 16, 2015 @06:00PM (#9390983)
The ':' is optional when followed by a directive.

"Loop" is also a valid label on at least say MASM 5.0, just need to use /w0 to suppress the warning.

Re:Why did the original code for FIND.COM use lop as a label... by RodgerTheGreat on Thursday April 16, 2015 @05:28PM (#9390833)
The post says the colon is optional. Seems like a poorly thought-out syntax.
Re:Why did the original code for FIND.COM use lop as a label... by geocar on Saturday April 18, 2015 @10:34AM (#9399569)
Okay, so maybe "lop:ret" and "lop ret" can be parsed the same (agree about the poorly thought-out syntax), but I don't see why "loop:ret" needs to be parsed as "loop ret" unless the colon is actually whitespace in masm.