walkero
/
physfs
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Updated.

This commit is contained in:
Ryan C. Gordon 2004-09-26 13:16:06 +00:00
parent e0da355650
commit 221a2303be
1 changed files with 0 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
TODO
View File

@ -32,18 +32,13 @@ Some might be dupes, some might be done already.
- Why do we call it openArchive and dirClose? - Why do we call it openArchive and dirClose?
- Sanity check byte order at runtime. - Sanity check byte order at runtime.
- Every DIR_* function requires a malloc/free! - Every DIR_* function requires a malloc/free!
- Merge DirHandle and PhysDirInfo.
- Memory locking? - Memory locking?
- Clean up file code to match DirHandle cleanups.
- Find a better name than dvoid and fvoid. - Find a better name than dvoid and fvoid.
- Use something other than void * for platform file handlers.
- Can win32.c and pocketpc.c get merged? - Can win32.c and pocketpc.c get merged?
- There's so much cut-and-paste between archivers...can this be reduced? - There's so much cut-and-paste between archivers...can this be reduced?
- General code audit. - General code audit.
- Just make PHYSFS_file * a void * typedef so we don't have to allocate?
- Multiple write dirs with mount points? - Multiple write dirs with mount points?
- Deprecate PHYSFS_setSaneConfig and move it to extras? - Deprecate PHYSFS_setSaneConfig and move it to extras?
- PHYSFS_file should really be PHYSFS_File for consistency.
- (Re)move the profiling code in physfs.c. - (Re)move the profiling code in physfs.c.
- Why is physfsrwops.c cut-and-pasted into the ruby bindings? - Why is physfsrwops.c cut-and-pasted into the ruby bindings?
- maybe other stuff. - maybe other stuff.