|
Finally some peace and quiet. Now you can bear down on your coding. This will surely last all evening, without interruption.
You reopen one of your ~ATH projects you started recently. You are still horsing around with the conditions for terminating the loops.
What many ~ATH coders do is import finite constructs and bind the loops to their lifespan. For instance the main loop here will terminate on the death of the universe, labeled U. That way you only have to wait billions of years for it to end instead of forever.
You have bound a subloop to the lifespan of the code's author, which is you. Any routine at the end will execute when you die. You figure this might be handy for coding something to release a final will and testament. Or maybe some doomsday virus. You spend a lot of time thinking of ways to make the perfect doomsday virus.
Conveniently absent from ~ATH's extensive import library are entities with short lifespans. Like a rapidly decaying particle that only lasts a millisecond sure would be handy. Or even a fruit fly or something. But no, coding with this language is all about finding ways to trick it into doing what you want.
Your hacker buddy is obnoxiously good at it. He's sent you some files which you still don't understand, but you're not going to admit that. He is even better at making viruses than you, which really gets stuck in your nook.
|
|
