<< Previous Message Main Index Next Message >>
<< Previous Message in Thread This Month Next Message in Thread >>
Date   : Mon, 25 Jul 2011 20:48:42 +0100
From   : jgh@... (J.G.Harston)
Subject: Risc PC (Was 'Minitel in France')

Rick Murray wrote:
> One that used to annoy me was it was possible to decode a 1900-era time
> from a FileStore with a failed battery. I'm not sure what or how, given
> such a time is "illegal" in the Econet sense, however:
>    SYS "NetFS_DoFSOp", 16, fstime%, 5, 5
>    SYS "NetFS_ConvertDate", fstime%, rotime%
> would cause a failure. The FileStore shouldn't return bogus dates, but I
> guess it can. I'd like to think DoFSOp would sanitise results, but I
> rather suspect it just passes data to and accepts from without much
> intervention. I wonder if/how the 6502 MOSs cope with this.

All FS_Op does is take the results from the server and pass it to the
calling program. It should not and *must* not interfer and impose its
own expectations on things. How is FSOp to know that FSOp 16 returns
a date, and that FSOp 18 doesn't? It's up to the fileserver to supply
sensible data and the calling code to cope with nonsensible results.

INPUT "Enter a date: "A$

How *DARE* the INPUT command not validate what the user has entered and
ensure it is a date???

-- 
J.G.Harston - jgh@...     
<< Previous Message Main Index Next Message >>
<< Previous Message in Thread This Month Next Message in Thread >>