|
On Fri, 15 Nov 2002, Hans Boldt wrote: > > However, there's still the issue of having one program call another. One > > standalone program cannot call another using a PLIST type of structure. Is > > that an issue? Only for us old OPM dinosuars. As the Hans's of the world > > drag us kicking and screaming into the newer models, we'll probably forget > > about the old PLIST entirely. > > Joe: The same issues of inter-program communication affect > programming in most OS's, as far as I can tell. But again, OS/400 > seems to be the odd one out in that parameter passing between > programs can indeed be bidi. The single level store probably has a > lot to do with that, since programs running in different processes I just had a thought on this: can't the same thing (passing parms from one executable to another and back again) be achieved using mmap? I haven't ever coded anything that used mmap and it might be a kernel space only function. But it does give a type of single level store for a limited memory space (meaning that two apps access the same memory area). James Rich
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.