[Info-vax] VMS Cobol - GnuCOBOL

[Dan Cross]

In article <k6btpvFu2e4U4 at mid.individual.net>,
bill  <bill.gunshannon at gmail.com> wrote:
>On 3/2/2023 8:14 AM, plugh wrote:
>> On Thursday, March 2, 2023 at 6:08:00 AM UTC-7, plugh wrote:
>>> On Wednesday, March 1, 2023 at 6:21:54 AM UTC-7, Johnny Billquist wrote:
>>>> On 2023-02-28 18:53, bill wrote:
>>>>> On 2/28/2023 12:04 PM, Denys Beauchemin wrote:
>>>>>> On Monday, February 27, 2023 at 7:11:36 PM UTC-6, Robert A. Brooks wrote:
>>>>>>> On 2/27/2023 6:35 PM, Arne Vajhøj wrote:
>>>>>>>
>>>>>>>> But isn't that the case for all VMS compilers? I know
>>>>>>>> I use /DEB/NOOP for both Fortran, Pascal and C when I want
>>>>>>>> to debug.
>>>>>>> Reagan may weigh in here, but I'm pretty sure that DEC suggested using
>>>>>>> /DEBUG/NOOP when using the debugger for any language with an
>>>>>>> optimizer back in
>>>>>>> the 80's; if so, then that's been a pretty consistent message.
>>>>>>>
>>>>>>> -- 
>>>>>>>
>>>>>>> --- Rob
>>>>>> Speaking of debuggers.
>>>>>>
>>>>>> I'm not clear on how you can actually debug a gnucobol program, since
>>>>>> it's C in reality.
>>> <snip>
>>>> Johnny
>>>
>>> Speaking of debugging GnuCobol (nee open-cobol)
>>> https://lists.gnu.org/archive/html/gnucobol-users/2009-06/msg00003.html
>>> I can't say why I never followed up. Anyway, it looks like the problem's been solved in the meanwhile.
>> 
>> Sorry, I think that was bill, not Johnny
>
>None of the included content was from me.  Not sure if any of it was
>from Johnny but I don't think so.

The proximal content was from Denys Beauchemin in
<be08c3cc-3990-401b-97d1-2cdf4ad92484n at googlegroups.com>.

The ">>>> Johnny" thing appears to be a text editing error,
because the response was cutting from many levels of quotation
(responses to responses to...).

	- Dan C.