--- swzoh wrote:
> Now I become skeptical about it, otherwise Bruce would have allowed
> this from the start, I wonder.
I believe Bruce made the second string a mandatory one because when
the syntax was introduced, it was intended only for executing programs
from a script.
> What might be a reason I can think of atm is the support for the
> internal commands "*...".
The Do() syntax can accept internal commands in any of the following
forms:
Do("*ShutDown", "Reboot NoConfirm Force")
Do("*ShutDown Reboot", "NoConfirm Force")
Do("*ShutDown Reboot NoConfirm", "Force")
Do("*ShutDown Reboot NoConfirm Force", "")
It seems that for these commands, PowerPro simply combines the two
strings anyway.
> Consider, e.g., Do("Note").
> Should PP search for "note.exe" or parse an internal command "*Note"
> to give an error of "missing ...".
We can already test this by executing Do("Note", ""):
�Invalid *Note Action:�
All in all, I don't think that making the second string optional will
cause any problems for anyone.
--
Alex Peters / Melbourne, Australia
PowerPro v3.8.16 / Windows XP
------------------------ Yahoo! Groups Sponsor --------------------~-->
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/JV_rlB/TM
--------------------------------------------------------------------~->
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/power-pro/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
