Re: [racket] open-output-file #:exist

2011-08-24 Thread Hendrik Boom
There was once work on an ISO standard for a "Software Bus", a set of relatively low-level primitive operations that would do just about everything you'd need to talk to an OS and which could be easily implemented with a lightweight software layer on just about any OS. It was torpedooed by the

Re: [racket] open-output-file #:exist

2011-08-24 Thread Matthew Flatt
Does anyone know a good reference to cite for this information? Like the details of TCP, I think this is something better explained by an external reference than in the Racket reference manual. Meanwhile, I'll look into smoothing the path from functions like `with-output-to-file' to information ab

Re: [racket] open-output-file #:exist

2011-08-24 Thread Stephan Houben
Hi Marijn, At least on Unix/Linux, a file (inode) has some distinct identity apart from its content. If a file is truncated, this is observed by all processes which have the file open. In addition, all hard-links to the file are also truncated (since these are just references to the same inode).

[racket] open-output-file #:exist

2011-08-24 Thread Marijn
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, In the reference in section 12.1.5 File Ports[1], open-output-file is defined as having an optional keyword argument #:exist which can have one of 8 different values. The same options are used for a number of wrapper functions, among which with-ou