From: "Dalton Spence" 
@Date: Tue, 14 Jan 2003 23:59:07 -0500
@Sender: semware-owner{at}sawasdi.apana.org.au



----- Original Message -----
From: "Fred Holmes" 
Sent: Tuesday, January 14, 2003 10:35 AM

> I can't see passing a command line parameter to an autoload macro from
the
> listing in the autoload list.  It would always be the same, so just write
> that parameter into the macro code itself (and rename the macro to
> distinguish it from the general one, if appropriate).   While I can't
think
> of a specific example right now, one could perhaps want to pass a command
> line parameter to an autoload macro from the g32.exe command line???

I go by the old programmer's saying, "Tis better to change a thousand
parameters than a single line of code." IAC, adding command lines to the
Autoload list provides a reason to add an edit function to its maintenance
procedure, and all for new features. :) As to the latter, this would
require some option to stop the program's processing of the DOS command
line so that a Query(DosCommandLine) could access data from after that
point.

--
              {at}=================================================={at}
              | Dalton S. Spence, B.Sc.  |
              | Home Page: http://www.hwcn.org/~ag775/home.html  |
              |      Family Motto: Virtute Acquiritur Honos      |
              | You must meet Jesus at San Francisco and get the |
              |              screaming jet. FNORD!               |
              {at}=================================================={at}


--
TSEPro mailing list



---
[sawasdi.apana.org.au] (3:800/846.13)