ctrl_z is a hold over from CP/M-80 at least. CP/M didn't have any sort of
counter or pointer to tell where the data ended in the last allocated disk
block, so a marker was used. I don't know why ctrl_z was chosen. Ctrl_\ , the
ASCII file separator charter would have seemed to be a better choice. I'm sure
they had their reasons.
Bruce
On Nov 11, 2011, at 9:43 AM, Mark Miesfeld wrote:
> On Fri, Nov 11, 2011 at 8:08 AM, Jean-Louis Faucher <jfaucher...@gmail.com>
> wrote:
> After replacing the test isDevice() by true, the open is ok, but...
> ...
>
> Tested under MacOs, looks good.
> Not tested under Linux or Windows.
> Not sure if I break something by not testing ctrl_z... For me, ctrl_z is
> Windows specific, no ? is the write-only mode supported under Windows ?
>
>
> Opening a file for write only is supported under Windows. ctrl_z is a hold
> over from DOS I think. I believe I read that the operating system ignores it
> now and goes by the size of the file. I.e. if you have a ctrl-z at position
> 100, but the file size is 200, the OS uses 200.
>
> I say commit the fix and I'll try to get some time to test it on Windows /
> look more closely at the ctrl-z issue.
>
> --
> Mark Miesfeld
>
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1_______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
