T.R | Title | User | Personal Name | Date | Lines |
---|
2633.1 | .EXIT or .ABORT called from within a structured block | IOSG::NEWLAND | Richard Newland, IOSG, REO2-F/J9 | Fri Apr 18 1997 19:15 | 10 |
| The .MSG source file defines the message as:
SCPNOBLOCKEXIT <.EXIT or .ABORT called from within a structured block>
This means that you are trying to leave a block of structured code, which
you are not allowed to do.
Richard
|
2633.2 | | IOSG::MAURICE | Back in the egg | Mon Apr 21 1997 08:56 | 10 |
| Hi,
Though you say the code ran under V3.0A, it can not have worked. Most
likely is that the .IF statement is catching an error condition that
has never occurred, so that the code after the .IF has never been
excecuted - or tested!
Cheers
Stuart
|
2633.3 | This should go under the "wild request" catagory but it came from the customer | ALFSS2::BEKELE_D | When indoubt THINK! | Wed May 07 1997 22:11 | 18 |
| Hi Stuart!
This customer has come back and is asking for documented advisory
on how CM has been tightened against sloppy code or those that are known
to us. In addition to this case of improper attempt to jump out of a
structured block, I can only think of such constructs as not having enough
.ENDIF in nested .IF statements or the change in the behaviour of .TEXT
directive in various versions of ALL-IN-1. This customer has many sites
as well as large amount of customized code and that they are holding out
on rolling out their upgrades unless they have modified their code that
is no longer ignored by ALL-IN-1.
Is there a more complete list that we can give to the customer?
Thanks!
Dan
|
2633.4 | | IOSG::MAURICE | Back in the egg | Thu May 08 1997 11:20 | 10 |
| Hi,
Sorry but there is no such list that I am aware of. The main other
change I remember was that the TXL compiler now catches lines in
scripts and boilerplates that are too long. This used to lead to
situations where uncompiled scripts worked, and compiled ones didn't.
Cheers
Stuart
|