Currently, the [* command is not implemented correctly. See this blog entry from June 6th:
Printing macros is done with the [* command. So, if XYZ is a macro meaning "hello!", then [*XYZ] prints "hello!"
Works correctly. But realized that definition of macros has to be passed through to the plugin. Currently, it's incorrectly being done by the Platypus parser, which does the macro definition operation at parse time.
Description
Currently, the [* command is not implemented correctly. See this blog entry from June 6th:
Printing macros is done with the [* command. So, if XYZ is a macro meaning "hello!", then [*XYZ] prints "hello!"
Works correctly. But realized that definition of macros has to be passed through to the plugin. Currently, it's incorrectly being done by the Platypus parser, which does the macro definition operation at parse time.
Actually, it's the [def command that has to be moved to the plugin. Currently, it's being done in the core Platypus processing. This means that by the time the list of tokens is passed to the plugin, the macros have the value of the last [def command.
Note: When done, note in the architecture manual that all plugins need to implement the [def command.
therealbean added a comment - 24/Jun/09 08:02 AM Actually, it's the [def command that has to be moved to the plugin. Currently, it's being done in the core Platypus processing. This means that by the time the list of tokens is passed to the plugin, the macros have the value of the last [def command.
Note: When done, note in the architecture manual that all plugins need to implement the [def command.
Task
Closed
Major
Need to implement [* command, which prints a user or system string
Actually, it's the [def command that has to be moved to the plugin. Currently, it's being done in the core Platypus processing. This means that by the time the list of tokens is passed to the plugin, the macros have the value of the last [def command.
Note: When done, note in the architecture manual that all plugins need to implement the [def command.