[Coco] "C" Compiler update project

[Stephen H. Fischer]

Hi,

Sorry, I thought about including more but decided not to. (I was working on 
the longer post at the same time and I really wanted the main message to be 
"I think that we need to vet the header files and libraries.")

Yes ENTER is defined as "'\r'" and my simple test case worked just fine.

So I will have to try ARCHIVE filling up a disk and see if the error message 
I saw does really appear as it should and why <CR> is not waited to be 
typed.

SHF


----- Original Message ----- 
From: "gene heskett" <gheskett at wdtv.com>
To: <coco at maltedmedia.com>
Sent: Wednesday, June 01, 2011 3:56 PM
Subject: Re: [Coco] "C" Compiler update project


> On Wednesday, June 01, 2011 06:55:10 PM Stephen H. Fischer did opine:
>
>> Hi,
>>
>> In compiling "Archive" I needed to add "FALSE", "TRUE" and "ERROR" to
>> "stdio.h"
>>
>> I am beginning to wonder if the failure to wait for a <CR> is due to
>> another difference in header files or in the "clib.l" library.
>>
>> It may also be another difference in C_Prep19b.
>>
>>    while(getchar() != ENTER);
>>
> Huh?  'ENTER' had better be defined someplace so that it actually aliases
> back to the os9 carriage return, aka a '\r'.
>
>> I think that we need to vet the header files and libraries.
>>
>> In order to do so, we need a place that the potential header files and
>> libraries are available so we can check our copies with them and then
>> make suggestions.
>>
>> SHF
>>
>
>
> -- 
> Cheers, Gene