[Coco] Valid file names for Disk BASIC

[Mathieu Bouchard]

Well, if in practice "0" works, then it must be an error in the manual, 
probably from confusion with a byte containing the value 0, which is what 
CHR$(0) gives you.

See in DECB manual, page n˚59, top-left, it says that if the first char is 
CHR$(0), the it means a deleted file, and if it's CHR$(255), it means a 
slot never used since formatting.


Le 2016-04-08 à 17:41:00, Salvador Garcia a écrit :

> Maybe?
>
> The following image was taken from page 10 of the official Tandy Disk Drive documentation:
>
> It does not really read as char(0), rather just as the char 0. But all is good :-) Thanks, I appreciate you getting in touch with me. Salvador
>
> -----Original Message-----
> From: Mathieu Bouchard <matju at artengine.ca>
> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>; Salvador Garcia <ssalvadorgarcia at netscape.net>
> Sent: Fri, Apr 8, 2016 2:57 pm
> Subject: Re: [Coco] Valid file names for Disk BASIC
>
>
> Doesn't it mean the NUL character, which is CHR$(0) ?
>
> Le 2016-04-07 à 15:13:00, Salvador Garcia a écrit :
>
>> Thank you all. All explanations were very clear. I am not sure what to
>> make out of the "zero" not allowed indication. The only reason why this
>> could be is that long ago the zero and oh were similar (or same)
>> character, so there were instances where the "0" char was not allowed to
>> avoid confusion, but does not make sense for a modern era computer.
>> Since the "0" char has been used successfully, I can easily dismiss it
>> as it having some other meaning. Again thanks! The Unraveled explanation
>> was particularly interesting. Regards, Salvador
>
>  ______________________________________________________________________
> | Mathieu BOUCHARD ---------- tél: 514.623.3801 ---------- Montréal, QC
>

  ______________________________________________________________________
| Mathieu BOUCHARD ---------- tél: 514.623.3801 ---------- Montréal, QC