I would like to get more informations concerning Directives. e.g.: !!TRACE option ? what are "option" values ? !!DEBUG option ? !!OPTIONS option ? !!SIZE CODE newsize ? what is newsize ? how to define the value ? Thanks for your help. Regards.

I would like to get more informations concerning Directives. e.g.:
!!TRACE option ? what are "option" values ?
!!DEBUG option ?
!!OPTIONS option ?
!!SIZE CODE newsize ? what is newsize ? how to define the value ?
Thanks for your help.
Regards.

Parents

0 Ken Walker over 6 years ago

Your TRACE and DEBUG questions are answered a little further down in the PCL and Customization document. (Look under Finding Programming Errors with PCL).

There are three options that can be enabled in TRACE; they are CALLS, EXITS, and LINES. Settings do this:

!! TRACE NONE (disables tracing)

!! TRACE CALLS (enables tracing of function calls)

!! TRACE NOCALLS (disables tracing of function calls)

!! TRACE EXITS (enables tracing of function exits)

!! TRACE NOEXITS (disables tracing of function exits)

!! TRACE LINES (enables tracing of function statements)

!! TRACE NOLINES (disables tracing of function statements)

You can combine them like this:

!! TRACE CALLS EXITS

Here are details on DEBUG:

With DEBUG ON, the original source lines of the file are compiled into the function. This allows the TRACE command to display the source during execution. The DEBUG option should only be used during development as it

creates much larger and slower code. The format of the DEBUG directive is:

!!DEBUG ON (enables DEBUG lines during compile)

!!DEBUG OFF (disables DEBUG lines during compile)

I don't have any info on !!OPTIONS or !!SIZE.

I don't think I have ever used either in 25 years of PCL authoring. Seriously.

Two you didn't mention that are pretty handy: !!LIBRARY CREATE and !! LIBRARY MERGE

You can use if you have several .pcl files, and want to compile them into matching .pob files , then merge all the .pobs into a single .plb file. This is typically handled with make and a Makefile so you only recompile the .pcl files that change as you work on a project.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Ken Walker over 6 years ago

Your TRACE and DEBUG questions are answered a little further down in the PCL and Customization document. (Look under Finding Programming Errors with PCL).

There are three options that can be enabled in TRACE; they are CALLS, EXITS, and LINES. Settings do this:

!! TRACE NONE (disables tracing)

!! TRACE CALLS (enables tracing of function calls)

!! TRACE NOCALLS (disables tracing of function calls)

!! TRACE EXITS (enables tracing of function exits)

!! TRACE NOEXITS (disables tracing of function exits)

!! TRACE LINES (enables tracing of function statements)

!! TRACE NOLINES (disables tracing of function statements)

You can combine them like this:

!! TRACE CALLS EXITS

Here are details on DEBUG:

With DEBUG ON, the original source lines of the file are compiled into the function. This allows the TRACE command to display the source during execution. The DEBUG option should only be used during development as it

creates much larger and slower code. The format of the DEBUG directive is:

!!DEBUG ON (enables DEBUG lines during compile)

!!DEBUG OFF (disables DEBUG lines during compile)

I don't have any info on !!OPTIONS or !!SIZE.

I don't think I have ever used either in 25 years of PCL authoring. Seriously.

Two you didn't mention that are pretty handy: !!LIBRARY CREATE and !! LIBRARY MERGE

You can use if you have several .pcl files, and want to compile them into matching .pob files , then merge all the .pobs into a single .plb file. This is typically handled with make and a Makefile so you only recompile the .pcl files that change as you work on a project.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data