carlito913 / editor-on-fire

Automatically exported from code.google.com/p/editor-on-fire
Other
0 stars 0 forks source link

Consider using Allegro file functions in the EOF port of FoFLC #208

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
FoFLC uses the standard C file functions, which (at least in Windows) don't 
support filenames with special characters.  Since I already have FoFLC's file 
I/O abstracted into error catching functions, it should be easy for me to add 
conditional compiling for the EOF version to use the PACKFILE functions.

Original issue reported on code.google.com by raynebc on 19 Nov 2010 at 3:54

GoogleCodeExporter commented 8 years ago
I don't think this is feasible in Allegro 4.  Allegro 5 does seem to have some 
file I/O functions that allow seeking forward and backward, so I'm going to 
consider that a bare minimum requirement of accomplishing this.  So this will 
be on hold until EOF is ported to Allegro 5.

Original comment by raynebc on 24 Oct 2011 at 11:29

GoogleCodeExporter commented 8 years ago
Alternatively I can use the file buffering IO logic I implemented for GH import.

Original comment by raynebc on 18 May 2012 at 6:39

GoogleCodeExporter commented 8 years ago
Using the buffering logic would likely work, I may just need to replace some of 
the functions that relied on Allegro.  Getting a file's size, for example, 
would need to be done as such:

fseek(fp, 0, SEEK_END);
size = ftell(fp);
fseek(fp, 0, SEEK_SET);

That would require the file handle to be open in binary mode though.

Original comment by raynebc on 26 Jul 2012 at 7:37