home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Black Box 4
/
BlackBox.cdr
/
bbs_opus
/
oac121.arj
/
OACOMP.115
< prev
next >
Wrap
Text File
|
1990-05-01
|
2KB
|
35 lines
Changes for version 1.15:
OACOMP 1.14 would allow packing of repeatable characters to result
in a count of 10, 13 and 16. OPUS chokes on this. OACOMP 1.15 now
packs the character sequence '..........' (10 periods) to 1 period
followed by a repeat count of 9 periods.
You can now define colour codes with the [$<hex>] construct, which
will emit a ^V^A sequence followed by the byte you specify, ie. to
swicth to yellow on black, just type [$0E], to switch to white on red
just type [$4F]. If you define any code with the 7th bit set, it will
be emitted with the 7th bit reset, and followed by a ^V^B to turn on
blink, ie. [$8F] will emit ^V^A^O^V^B. To change only foreground or
background, you can use [$?E] or [$0?].
The .KWD file in OAC114 was in error. Here are the corrections:
^OF On exit do this file next. [ONEXIT]
^OY Return from OEC now. * [EXIT]
You can now have local token extensions. By placing a .TOK file in
the same directory as the .OEC file and with the same name, all the
tokens defined in there will be available when compiling the .OEC
file, ie. C:\OEC\TEST.OEC would need C:\OEC\TEST.TOK. All the tokens
defined in the local token file has priority over the global token
file, which again has priority over the internal tokens.
You can now use tokens in your own tokens. Previously, the tokens
you defined were text tokens, ie. no compilation were performed on them.
Now the token value are sent through the compiler for compilation.
This means that you can redefine the tokens as you wish, or even make
macro tokens, like:
HEADER [CLS]This is a [SAVE][$0E]header[LOAD] on a clear'ed screen.