From a practical usage standpoint, I'd like to hear what the users
here think about routine use of $SEGMENT breaks in MAIN moudules.
I've done as good a job as I can do at breakapart of code work as
seems practical for my mix of PBU's and common source library work.
But with almost a dozen major executables now way up in the 25,000
line range, I'm reaching the point where there is just so much that
has to go on in MAIN, that it just isn't coherent for maintenance
work planning to keep trying to chop up what really is the MAIN logic
of the executable, just to keep MAIN down below 64K.
Yes, I realize that an overview of the whole MAIN module does in fact
lead to better places where a $SEGMENT can be placed, among perhaps
a number of 'proper' places that it might be placed.
But a real nagging question, after seeing what subtle shifts of a
$SEGMENT that shouldn't be needed below 64K, but are, to just get things
to run or stabilize a project, is; what's the practical experience of
some of the crew here in deliberately using them to extend what needs
to be done in MAIN beyond 64K?
Of course, from a tool design standpoint, it shouldn't make a differece
if you use the technique as it is supposed to be used! And there are
those who would be critical of ever trying to do things in large
executables as opposed to skaty-eight tiny modules that all do this
and that. What I want to learn about is the experience of those
here that are actually using the $SEGMENT technique deliberately to
extend the capability of a > 64K MAIN design. That as well as any
official comments on things that may help to assist me in making the
decisions on how and where to place such a deliberate fence between
pastures here!
No guarantees needed, just thoughts - please.
For example; is it better design to place a $SEGMENT between the
major setup, dimensioning and include code, than, for example, just
ahead of all the error trap routines at the bottom of the MAIN?
If you, as I do, for example, coddle all by BTRIEVE work in a major
block of 'standardized' routines, should I contemplate the use of
a $SEGMENT immediately before or after that major block?
Why has this surfaced?
An in-practice position as to security of access for program operations
is now being thrust upon us. Just the additional level of in-program
security and logging checks and trace traps now being 'required' or
soon to be so in the near future, is markedly adding to what I'm being
forced to consider for 'normal' operations here.
Help me contemplate the future of who iz, why, when and where?
Thanks.
------------------
Mike Luther
[email protected]
here think about routine use of $SEGMENT breaks in MAIN moudules.
I've done as good a job as I can do at breakapart of code work as
seems practical for my mix of PBU's and common source library work.
But with almost a dozen major executables now way up in the 25,000
line range, I'm reaching the point where there is just so much that
has to go on in MAIN, that it just isn't coherent for maintenance
work planning to keep trying to chop up what really is the MAIN logic
of the executable, just to keep MAIN down below 64K.
Yes, I realize that an overview of the whole MAIN module does in fact
lead to better places where a $SEGMENT can be placed, among perhaps
a number of 'proper' places that it might be placed.
But a real nagging question, after seeing what subtle shifts of a
$SEGMENT that shouldn't be needed below 64K, but are, to just get things
to run or stabilize a project, is; what's the practical experience of
some of the crew here in deliberately using them to extend what needs
to be done in MAIN beyond 64K?
Of course, from a tool design standpoint, it shouldn't make a differece
if you use the technique as it is supposed to be used! And there are
those who would be critical of ever trying to do things in large
executables as opposed to skaty-eight tiny modules that all do this
and that. What I want to learn about is the experience of those
here that are actually using the $SEGMENT technique deliberately to
extend the capability of a > 64K MAIN design. That as well as any
official comments on things that may help to assist me in making the
decisions on how and where to place such a deliberate fence between
pastures here!
No guarantees needed, just thoughts - please.
For example; is it better design to place a $SEGMENT between the
major setup, dimensioning and include code, than, for example, just
ahead of all the error trap routines at the bottom of the MAIN?
If you, as I do, for example, coddle all by BTRIEVE work in a major
block of 'standardized' routines, should I contemplate the use of
a $SEGMENT immediately before or after that major block?
Why has this surfaced?
An in-practice position as to security of access for program operations
is now being thrust upon us. Just the additional level of in-program
security and logging checks and trace traps now being 'required' or
soon to be so in the near future, is markedly adding to what I'm being
forced to consider for 'normal' operations here.
Help me contemplate the future of who iz, why, when and where?
Thanks.
------------------
Mike Luther
[email protected]
Comment