-=> Quoting Dan Sullivi to Phil Roberts <=-
 PR> No, I didn't say anything like that.  I try not to "step on"
 PR> Fred's values in "my stuff".
 DS> I don't see anything wrong with "stepping on" Fred's values.
 DS> I thought that was the whole purpose of a very configuratable
 DS> program... Fred can have his values, we can change them (or leave them
 DS> as-is) as need be.
There are no sacred cows here either.  :-)
 DS> I'll ask directly...
 DS> Which takes precedence if I have a certain thing configed twice (to
 DS> different values)? The first instance, or the second?
Apparently, if the entire macro executes, the second occurance
would change the value, just like a variable in a program.  Of
course, you have to look at the flow of the macro, since a line
may never execute at all.
 DS> I wanted to leave Fred's values in place (for reference purposes) (or
 DS> in case I need to later "undo" my changes).  And then just *ADD* mine
 DS> in there too.  But should they go BEFORE Fred's or AFTER? -!- CNet/3
If you want to change the value, do it after or just don't
execute Fred's lines.  Better yet, rename Fred's COMMO.MAC
COMMONEW.MAC or some other name that you aren't going to use.
Then, cut/paste whatever you like and leave the rest.  I've done
this many times.  :-)
The biggest change I remember in the recent history of the
program was to leave the main macro active even when other macro
files are loaded with macl.  I don't remember which version this
started with.
                                Phil
... File Not Found.  Backup Not Found.  Sure you don't want a drink?!
--- PoP/GEcho+/Telegard
---------------