Monday, January 7, 2019

How many chat codes are their?

Chat codes are fun to write, now we make them all useful, give them a rectangle, an io manger thread.   Swap you chat snippet on the fly when you want to go over code or equations or bitmaps; you tell the counter party to meet you at the bitmap rectangle ans show him your bitmap. isis stuff they do with Jupyter notebook.  The newer standard has args list space reserved per window, and direct memory sharing model works over he network. So a lot of the chats will move to that method, and chats are not just for humans, the high level engines swap messages with each their using shared memory model on args.

The consensus snippet arbitrates access to competitive claims on a section of args. Console loop remains the simple DMA controller in the model and will defer to the consensus snippet as syntax requires it.  Console loops are siple because the user manual requires Turing complete, else you have to issue a new thread and permanently reserved args. So the logic is always, it should have folded back up and left console loop in the initial state, thus preserving args and argc.

What about snippets and memory leaks?

Run the memory leak snippet prior to certain tagged linux commands. Part of generals snippet testing.  We can also test against argc errors by running the special argc guard code on tagged linux commands.  Once the snippet authors see the opportunity, they respond with special skills. Some of the pros will produce quick snippets to diagnose  all sorts of problems. Data manager can run snippet tests before deploying.   Snippet authors fee to work at home under this model,developing proprietary snippets targeted to an enterprise.

In many cases he best bet is a recompile of all 800 lines of console loop with the test flag defined. Then deploy that where you think problems lie. Snippets are small, everywhere small and complete, easily tested with a recompile and debug set, or recompiled to run in standalone test. We stick to the lowest level in snippet land because we can see, on a snippet basis, what one small section of args list is doing, a complete view at the terminal end of enterprise semantis.

No comments: