That deepends on what you mean by debugging facilities. PL/I has features bthat
help in debugging, but a good debugger has a lot more.
Shmuel (Seymour J.) Metz
From: IBM Mainframe Assembler List <ASSEMBLER-LIST@listserv.uga.edu> on behalf
of Robin Vowels <robi...@dodo.com.au>
Sent: Thursday, February 1, 2018 4:02 AM
Subject: Re: Fair comparison C vs HLASM
From: "Jon Perryman" <jperr...@pacbell.net>
Sent: Thursday, February 01, 2018 1:49 AM
> On Wednesday, January 31, 2018 1:00 AM, Robin Vowels <robi...@dodo.com.au>
> From: "Keith Moe" <ke...@sbcglobal.net>
> Sent: Tuesday, January 30, 2018 11:08 AM
>>> Keith Moe wrote:
>>> One of the downsides to such great optimization
>>> is the added difficulty in debugging.
>> Robin Vowels wrote:
>> Such optimisations are rarely requested
>> during debugging, when all the facilities of the
>> compiler - such as subscript bounds checking,> check for uninitialized
>> variables, etc, are
> Keith is talking about dump analysis.
But even if he was, the link map and assembly listing deals with that issue.
However, as I said, optimising is not usually requested during debugging.
> Think of optimization as a chaotic programmer. The stronger the
> optimization, the more chaos.
> The best optimization will often make following the machine logic very
The last time I used a dump to find bugs in a compiled program was about 35
PL/I provides all the information required because it has debugging facilities
This email has been checked for viruses by Avast antivirus software.