Opened 14 years ago

Last modified 14 years ago

#103 closed enhancement

Add compilation switch to control which file I/O back-end to use in PJLIB — at Version 1

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 (last modified by bennylp)

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), causing subsequent opening file to fail.

On Win32, we have alternative back-end of file I/O using Win32 native file operations (CreateFile?(), ReadFile?(), etc.), which doesn't have this limitation, but unfortunately this backend implementation is not being used.

So PJLIB should have a compilation switch to enable which file backend to be used.

Thanks David Clark for pointing this out.

Change History (1)

comment:1 Changed 14 years ago by bennylp

  • Description modified (diff)
Note: See TracTickets for help on using tickets.