[06 Jun 2009] Compiler output

[Simon]

Note: This is an archived post that was originally sent to the Hollywood mailing list on Sat, 06 Jun 2009 15:59:24 +0100

I have come up against a bit of a stalling point with my CodeBench plugin for Hollywood, due to the fact that the command line compiler wants to chuck it's output to its own console window, rather than the default output stream. This leaves me with a problem, that I cannot show the output in my own build window with error linkage etc.

So, is there anyway to get the compiler to use the stdout stream so that I can push it down a pipe?

Simon

[airsoftsoftwair]

Note: This is an archived post that was originally sent to the Hollywood mailing list on Sat, 13 Jun 2009 17:08:08 +0200

Sorry for the delay... I was away from home for some days.

I have come up against a bit of a stalling point with my CodeBench plugin for Hollywood, due to the fact that the command line compiler wants to chuck it's output to its own console window, rather than the default output stream. This leaves me with a problem, that I cannot show the output in my own build window with error linkage etc.

So, is there anyway to get the compiler to use the stdout stream so that I can push it down a pipe?

Yes, this is possible by using the -debugdevice argument together with @stdout. E.g. to redirect output to t:hw.out simply call:

Code: Select all

1> Hollywood >t:hw.out myscript.hws -debugdevice @stdout

[Simon]

Note: This is an archived post that was originally sent to the Hollywood mailing list on Thu, 18 Jun 2009 01:35:17 +0100

Yes, this is possible by using the -debugdevice argument together with @stdout. E.g. to redirect output to t:hw.out simply call: 1> Hollywood >t:hw.out myscript.hws -debugdevice @stdout

That's brilliant, I now have the output in my build window. I just need to filter out the escape sequences now

Simon

[airsoftsoftwair]

Note: This is an archived post that was originally sent to the Hollywood mailing list on Thu, 18 Jun 2009 11:21:07 +0200

That's brilliant, I now have the output in my build window. I just need to filter out the escape sequences now

Great! By the way: If you use -debugdevice, errors will not be displayed using a system requester either but they will come in through stdout, too. The format is the following:

<file>:<line>: <error message>

e.g.

dh0:Hollywood/Examples/Welcome/Welcome.hws:120: Cannot open brush logo.iff!

You could use this information to highlight the line that's erroneous.

[Simon]

Note: This is an archived post that was originally sent to the Hollywood mailing list on Thu, 18 Jun 2009 19:32:44 +0100

Great! By the way: If you use -debugdevice, errors will not be displayed using a system requester either but they will come in through stdout, too.

OK, that's even better.

The format is the following: <file>:<line>: <error message> e.g. dh0:Hollywood/Examples/Welcome/Welcome.hws:120: Cannot open brush logo.iff! You could use this information to highlight the line that's erroneous.

Yes, the plugin will parse the error lines and determine which file and line to jump to, exactly like the C/C++ plugin does now.

Do you have any objections to me embedding your help texts and command reference in the plugins help system too? I haven't finished the help system yet, but it will be based on a binary file with a jump table that the plugin can use to obtain function reference etc when the user requests it. The problem is, it will be lots of work to automate this task, so it's easier for me to build the database file by hand, and include it with the plugin.

Just as there is a "free" licence version of CodeBench for the OS4 SDK, I'm planning on releasing a "free" licence version just for Hollywood. This will work like the SDK version, where it is tied to just the one plugin. The full commercial version will be able to use any plugin the user wants, even simultaneously.

Simon

[airsoftsoftwair]

Note: This is an archived post that was originally sent to the Hollywood mailing list on Fri, 19 Jun 2009 00:19:53 +0200

Yes, the plugin will parse the error lines and determine which file and line to jump to, exactly like the C/C++ plugin does now.

Very good!

Do you have any objections to me embedding your help texts and command reference in the plugins help system too? I haven't finished the help system yet, but it will be based on a binary file with a jump table that the plugin can use to obtain function reference etc when the user requests it. The problem is, it will be lots of work to automate this task, so it's easier for me to build the database file by hand, and include it with the plugin.

Well, the help texts shouldn't be part of the plugin. These should be only available to Hollywood owners. But you can easily generate them from the Hollywood.guide because I've followed strict guide lines: The nodes in the Hollywood.guide always correspond to the function name. So the help text for DisplayBrush() is in a node named "DisplayBrush" etc. If you keep a list of all Hollywood functions in your plugin, you can easily iterate over them and extract the corresponding help texts from the Hollywood.guide which always resides in Hollywood:Help.

The syntaxes of all functions can of course be included but for the help texts: please generate them dynamically from Hollywood.guide during installation or even on-the-fly.

Just as there is a "free" licence version of CodeBench for the OS4 SDK, I'm planning on releasing a "free" licence version just for Hollywood. This will work like the SDK version, where it is tied to just the one plugin. The full commercial version will be able to use any plugin the user wants, even simultaneously.

Sounds good! I hope that Hollywood support increases CodeBench sales

[Simon]

Note: This is an archived post that was originally sent to the Hollywood mailing list on Thu, 18 Jun 2009 23:34:08 +0100

Very good!

Talking of which, is there a list somewhere of all possible output on an error or a warning? I just need to make sure I can handle all eventualities without creating every fault I can find

The syntaxes of all functions can of course be included but for the help texts: please generate them dynamically from Hollywood.guide during installation or even on-the-fly.

Ok, that's fair enough, although I doubt anyone but Hollywood owners will be purchasing the plugin. Nevertheless, the guide format should make it much easier to parse.

Sounds good! I hope that Hollywood support increases CodeBench sales

Not by giving it away it won't

Simon

[airsoftsoftwair]

Note: This is an archived post that was originally sent to the Hollywood mailing list on Fri, 19 Jun 2009 16:13:53 +0200

Talking of which, is there a list somewhere of all possible output on an error or a warning? I just need to make sure I can handle all eventualities without creating every fault I can find

No, that's all. If an error happens outside a script, there'll be no information on file/line at all. You will then just get something like:

Cannot open asl.library!

etc.

But these errors should not happen too often. Most errors will be related to the current script and they will always be in the <file>:<line>: <error message> format.

[airsoftsoftwair]

Note: This is an archived post that was originally sent to the Hollywood mailing list on Thu, 02 Jul 2009 18:22:41 +0200

Not by giving it away it won't

By the way: If you want to highlight inbuilt commands and constants in the CodeBench plugin, you could generate them on the fly by using some undocumented Hollywood functions. The PRIVATE1 argument exports all inbuilt commands to the specified file, the PRIVATE2 argument does the same with all inbuilt constants, e.g.

Code: Select all

1> Hollywood dummy.hws -private1 ram:cmds.txt -private2 ram:csts.txt

Note that a dummy filename must be specified although it is ignored.

You could then parse the files cmds.txt and csts.txt and import these commands & constants into CodeBench. The advantage of this approach is that the plugin would automatically recognize future commands and constants of Hollywood... this makes it a lot easier for you to maintain the plugin because you don't have to search through the history to detect every little change... just as a suggestion

[Simon]

Note: This is an archived post that was originally sent to the Hollywood mailing list on Thu, 02 Jul 2009 17:29:16 +0100

You could then parse the files cmds.txt and csts.txt and import these commands & constants into CodeBench. The advantage of this approach is that the plugin would automatically recognize future commands and constants of Hollywood... this makes it a lot easier for you to maintain the plugin because you don't have to search through the history to detect every little change... just as a suggestion

And a very good one at that, thanks. I shall look into that once I finish the "Help-as-you-Type" feature.

Simon