Without getting into numerical number systems, assembler C macros with threads/fibers without using gcode. But that might just be a macs thing with/without enc

Without getting into numerical number systems, assembler C macros with threads/fibers without using gcode. But that might just be a macs thing with/without enclosures, depending upon how parsed. Future C++ standard might relegate that into obsolescence, unless an infinity fabric of busy beavers crashes all computer multiverses first. Much more clarity/simplicity with a 'halt, catch fire' closure than enumerating every possible applicative option. ** Where art / science / engineering intersect/diverge/merge/differ? *** Obsolete's the necessity of a coder, scripter and programmer walking into a bar, at least in theory. For a given use case, depends on the IDE / framework using to unwind the stack. To much stack foo, and software developer will likely wind up walking into the bar and generate/raise an Exception to handle the issue at a later point in time.