> BTW An alternative solution to implement this syntax might be adding a
> definition of custom "scripts label call character" in
> setup>characters. But I think that this may introduce even more mess.

(and now little fiction :-) )
I have now yet another idea, so user can define own syntax for
every(!) command in PP - I mean creating special command list
"HookPPCommandExecution" hooked to every command before execution by
PowerPro, so user can write own command parser.
So any calls (.script.label or any else syntax even
[EMAIL PROTECTED]) may be translated (parsed) by user script to
native PP format and then executed.
This would be a totally advanced approach.
Of course I known that this is rather visionary than practical,
because maybe only few orthodox users (like me ;-)) would use this,
but it this is another idea how to implement new independent syntaxes
without implementation in PP.


Attention: PowerPro's Web site has moved: http://www.ppro.org 
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/
 



Reply via email to