quote:
Originally posted by LCC:
That stuff would be done by macrocommands invoking system functions through the engine interface "calldown". Depending on the relative address range of a processor, a macrocommand file can be as big as you like and have as many functions in it as needed. Just one of the functions needs to link up to the chain - the one named after the file and the same as the command name that invoked the file.
Shared data storage space is obtained off calls (through calldown) to system functions for memory at runtime, then the address of the data obtained is stored in data structures defined by the macrocommand designer. The address of the structures is placed in ADB entries and pulled out by the ones who need to share data pointed to. Do I really need to explain trivial stuff like this?
IF the tools to do the same sort of programming that you grew accustomed to on the PDP-11 were available for Wind'oohs you'd have a chance of being correct. Once you check into what must actually be used to program in Wind'oohs these days you will realize that there's nothing 'trivial' about programming anymore. "Hello, World" will probably come out to several hundred kbytes on most contemporary MS compilers. Now, if you can find the tools you want in a *IX environment -- not impossible since the *IX systems are much better at preserving 'legacy' software -- and can write a decent program for Gnu/Linux and/or FreeBSD in the style you describe you might have something. Every little bit helps to increase the popularity and power of the free OSes.
Re: OT = How Does Shrapnel Stay In Business
Threaded Mode