On Fri, 4 Sep 2020 20:38:29 +0000, Robert Prins wrote:
>On 2020-09-04 17:01, Paul Gilmartin wrote:
>> I see everything twice:
>> On Fri, 4 Sep 2020 19:05:32 +0000, Robert Prins wrote:
>> On Fri, 4 Sep 2020 19:06:49 +0000, Robert Prins wrote:
>
>Yes, problems posting. Should be OK now.
>
Your setting your system clock to Europe/Vilnius but calling it UTC
remains an irritant to those who want to read threads in chronological
sequence. I suppose you relish your plies' floating to the top of the
list for a couple hours.
> ...
>However as a Pascal partisan, you should love(?) the NOLAXQUAL compiler option,
>one of the options (when used) that takes away one of the best features of
>PL/I,
>which is that as long as the compiler can uniquely find a variable in its
>symbol
>table, you do not have to fully qualify it. Wit the the NOLAXQUAL compiler
>option you will have to use myvar.thislevel.array.struct.variant.plorkestein,
>even if "plorkestein" is the only variable in the program with that name, which
>is one of the worst features of Pascal.
>
Can't be as bad as the lack of static initialization.
And somewhat mitigated by the WITH statement.
I understand that PL/I tolerates fairly arbitrary permutation of
qualifiers as long there's a unique valid depermutation. I.e.
struct.array[I] and strict[I].array are alternatives. An invitation
to obscure coding. C is bad enough for making array[I]
equivalent to I[array].
We confronted a cadre of PL/I partisans who strenuously objected
to the NOLAXQUAL-ness of IEEE Pascal. They reacted by providing
a standard header containing a WITH to expose the penultimate
level of every structure. And we scrambled to revise our code
generator to fix the resulting base register exhaustion.
I once wrote a Pascal program to convert RTF to SCRIPT/VS. A
co-worker enthusiastically grabbed it, only to be dismayed that I
had relied heavily on the IEEE standard file buffer that was
unsupported by the Turbo he used. Borland boasted of the
misfeature.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
