File I/O development - Githubissues

brianfeaster / worldtm

Automatically exported from code.google.com/p/worldtm

0 stars 0 forks source link

File I/O development #14

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

File I/O is not entirely implemented. It is possible to open and read/write an 
existing file but a new file can't be opened.

I/O based on local file descriptors as well as standard I/O file pointers are 
used.  I/O related code needs to be cleaned up and homogenized.

File and socket I/O unit tests need to be created.

Original issue reported on code.google.com by bri...@gmail.com on 11 Aug 2010 at 6:58

GoogleCodeExporter commented 8 years ago

r52 implements new file creation.

Original comment by bri...@gmail.com on 19 Sep 2010 at 5:05

Changed state: Started
Added labels: Priority-Medium
Removed labels: Priority-High

GoogleCodeExporter commented 8 years ago

Setting to low priority.  Socket and file I/O have been cleaned up.  Still 
required are sane debug and debugging output which are a mixture of file 
descriptor, FILE pointer, raw and cooked modes.

Original comment by bri...@gmail.com on 26 Oct 2010 at 3:16

Added labels: Priority-Low
Removed labels: Priority-Medium

GoogleCodeExporter commented 8 years ago

The current state of error handling includes runtime checks for most system 
calls including file and socket I/O calls.

Original comment by bri...@gmail.com on 30 Oct 2011 at 8:21

Changed state: Fixed