Welcome to jBASE's new documentation site! Many answers to your questions can be found by searching the Knowledgebase or viewing the jBASE Documentation. We also have a Google Group for peer discussion about jBASE. If you are unable to find the information you are looking for, jBASE Support will be glad to assist in resolving your technical problems. Enjoy and please provide comments and feedback .

How can we help you?

PN5_60770

Description

Rationalise the way we set compiler options. 


Previous Release Behavior

Setting compiler options is a bit of mixed bag. 


Current Release Behavior

There are a number of options with which you can control the compiler. Some options control the operation of the compiler (including debug information), and some control the language aspect. This change rationalises the setting of options into a sane, useful and consistent manner. 

The options you can set may be detailed by executing the command jpp2 -h. You can add 'no' to the option to negate the option. 

The manner in which we decide options during compilation is now like this: 

1) If the file name ends in .jabba, we set the jabba option and turn off case sensitivity (i.e. we become case insensitive for keywords and variables). 

2) Any options in Config_EMULATE with the 'compiler_options = xxx' statement are processed. This was added for this change, and the Universe emulation now contains this 

compiler_options = universe

See PN5_60769 for a description of what the universe option gives. 

3) Any options in the 'JBC_JPP2' environment variable are now processed. 

4) Any options in the source code are processed for example: 

$option jabba,nocase

As an example, if you want to compile all the time without case sensitivity, this is the option you would add to Config_EMULATE 

compiler_options = nocase

You could also achieve this by setting the following environment variable: 

export JBC_JPP2=nocase   [Unix]
set JBC_JPP2=nocase      [Windows]

Note that for D3 emulations, this has been added as a default option and it now replaces the defunct option compiler_case_insensitive_variables_keywords = true

Was this article helpful?