I really enjoy Pth, and am using it's functions quite extensively in my mmftpd and mmmail servers (http://mmondor.gobot.ca/software.html or cvs -z9 -d:pserver:[EMAIL PROTECTED]/cvsroot co mmsoftware). I especially like it's event handling, which even POSIX threads don't provide. Here are notes of interest on things that I feel could be modified, I possibly could perform the changes myself as long as the community likes the modifications. Of course suggestions are first requested.
First, I noticed that pth_msgport_create(), although inspired from the AmigaOS API, does not support NULL for port identifyer, which would be very useful for thread-specific private message ports (mmftpd uses those and unfortunately currently has to generate unique strings to create ports). AmigaOS had this functionality... Another suggestion would be exporting the low-level pth_mctx_*() interface so that applications that only need portable context switching/manipulation features could possibly use it. Those could then be documented as well in the man page... For instance a real-time kernel scheduler implementation I have been working on a while back, could easily be tested on unix in a portable manner. It's unfortunate that the SVR4 API is not part of all unices, and that sigaltstack fiddling is architecture + platform dependant. But Pth has all this for us already, it's just not exported publically. Possibly that an SVR4-inspired public API could be made part of future Pth versions. Matt ______________________________________________________________________ GNU Portable Threads (Pth) http://www.gnu.org/software/pth/ User Support Mailing List [EMAIL PROTECTED] Automated List Manager (Majordomo) [EMAIL PROTECTED]
