And there no mechanism you can fix it.
If you now vote for something else, they just cancel the results and make you vote again.
1,571 karma · joined October 10, 2011
And there no mechanism you can fix it.
If you now vote for something else, they just cancel the results and make you vote again.
Originally you had to write inline assembly.
I was truly disappointed that Turbo Pascal did not copy my handy PORT-metavariable. You can write & read IO-ports without any extra hässle:
But it was just a grey box running Maclisp of sort. Never understood the actual purpose, except Amerikka novelty -- for Russian visitors in Helsinki,
I think Lisp in big VAX was faster or at least more convenient?
Insane, because this strait has always heavy current and nasty mælstrøms as half of Atlantic goes that way to east and back daily.
You can make random search N in the MP3-module, because OFF/ON restarts and then you short NEXT-button wires N times.
However, you had to be a programmer Anno Dominii 1975 to fully understand what heavenly Joy and Jubilation Z80 was.
Strange they did not make OpenSCAD in AutoLISP-style.
I have to read the manual all the time, because I never learn the weird syntax of OpenSCAD for-statement.
In so-called real life somebody has to live with the malformed macro, whose only purpose is to beautify the code.
I even made un-macrofier, which deleted all macros and replaced instances with macroexpand, because slight adjustement of code resulted mysterious errors cause by nasty macroes.
And lets not talk about Common Lisp loop macro, which was probably scooped up from latrine of hell by the Devil himself.
I am just saying that the end-user do not need macros for much anything, unless she has some specific optimization in mind. Bloody annoying when they start making cryptic macros to "extend the language".