Opened 17 years ago
Last modified 17 years ago
#103 closed enhancement
Add compilation switch to control which file I/O back-end to use in PJLIB — at Initial Version
Reported by: | bennylp | Owned by: | bennylp |
---|---|---|---|
Priority: | normal | Milestone: | release-0.5.10 |
Component: | pjlib | Version: | 0.5.9 |
Keywords: | Cc: | ||
Backport to 1.x milestone: | Backported: |
Description
The default file I/O back-end is to use ANSI stream API (fopen(), fread(), etc.), which works great since it is portable across platforms. However it has a limit of number of files that can be opened simultaneously (FOPEN_MAX).
On Win32, we have alternative back-end of file I/O using Win32 native file operations (CreateFile?(), ReadFile?(), etc.), but this has never been used.
Note: See
TracTickets for help on using
tickets.