Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#103 closed enhancement (fixed)

PJLIB should use Win32 file I/O back-end on Win32

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.

Thanks David Clark for pointing this out.

Change History (4)

comment:1 Changed 13 years ago by bennylp

  • Description modified (diff)

comment:2 Changed 13 years ago by bennylp

  • Description modified (diff)
  • Summary changed from Add compilation switch to control which file I/O back-end to use in PJLIB to PJLIB use Win32 file I/O back-end on Win32

comment:3 Changed 13 years ago by bennylp

  • Resolution set to fixed
  • Status changed from new to closed
  • Summary changed from PJLIB use Win32 file I/O back-end on Win32 to PJLIB should use Win32 file I/O back-end on Win32

Implemented in r950 and r951.

comment:4 Changed 13 years ago by bennylp

More in r955 (VS8 project for Release build was not updated).

Note: See TracTickets for help on using tickets.