|
> > From: Joel Cochran > > > > Instead of having fifty copys of the service programs > > and hence its global variables, then there is > > just one copy that gets accessed from fifty different places. > > The appearance is that the global variable is shared, > > but in reality it is the activation group that is shared. > > Hm. This is counter to what I always understood. > In my understanding, there were two different pieces > to any program: the code and the data. While each > job got its own data portion, the code portion was > shared, the caveat being you had to be in the same > memory pool. Your understanding is still correct. The bit that is missing is that the activation group is a subset of a job. AGs do not cross job boundaries. So now you can have separate 'data pools' within a job if you want by having the same program run in two AGs if you want to. --buck
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.
midrange.com
