I just triggered a Millennial

[d000hg]

I suggested implementing GO TO functionality in the rule engine syntax we're developing.

Off to the incinerator with me.

GOTO has been a source of ire long before Millenials were old enough to land jobs!

I only discovered recently C# now lets you switch on, well just about anything... random values, strings, object types.

You can now literally compare apples and oranges.

[OwlHoot]

GOTOs are for lightweights. What you really need are assigned GOTOs, and lots of them.

It's the programming equivalent of St Trinians girls hopping off their train, changing the points, hopping back on, and then heading off down a different set of tracks!

Shortly before leaving my first permie role many years ago, I wrote a vast COBOL program with loads of "ASSIGN TO PROCEED TO" statements, which are the COBOL equivalent.

[AtW]

GOTO is for amateurs.

Pros use JMP

[DoctorStrangelove]

GOTOs are for lightweights. What you really need are assigned GOTOs, and lots of them.

Yup, I was thinking that too.

Which I've only ever seen used in one program and I've never used it myself

[Zigenare]

Push the address on the stack and then return.


You lot really are amateurs.

[NotAllThere]

Push the address on the stack and then return.


You lot really are amateurs.

Pah. Read and write from the stack directly, you wuss.

[JamesBrown11]

Run the code through a minifier/obfuscator then hire an intern and tell him to refactor it

[NigelJK]

Once you've mastered the 'fashionable' GOTO band waggon, write some self modifying code.

[DoctorStrangelove]

One machine I used allowed one to build an instruction in a register and then execute it.

That was fun.

[Dark Black]

Don't forget recursion, they hate / don't understand that