Mail Archives: djgpp/2004/12/30/14:30:06
"Eli Zaretskii" <eliz AT gnu DOT org> writes:
> > From: David Bolen <db3l AT fitlinxx DOT com>
> > Date: 29 Dec 2004 14:46:25 -0500
> >
> > We use pmcom for our serial handling and find it works very nicely.
> > Unless you use something like this, the odds are very good that you'll
> > lose serial data since BIOS won't buffer any information but must be
> > polled to ensure you receive all data. While it doesn't directly
> > integrate into the filesystem layer in DJGPP, by and large
> > COMPortOpen, COMWriteBuffer and COMReadBuffer are pretty easy
> > replacements for open(), write() and read().
>
> One could integrate pmcom into the filesystem layer by using the DJGPP
> Filesystem Extensions feature (it is described in the library
> reference manual). Then you could simply use `open', `read', and
> `write'.
Right - I wasn't saying it couldn't be done, just pointing out that
the current pmcom library didn't make use of that facility (as opposed
to, for example, wattcp32).
> > You may be getting compilation errors due to some older preprocessor
> > string concatenation stuff that was in the source (at least in the 1.0
> > version we use). In our case it was fixable by editing com.c and
> > replacing instances of "##x" with just "x" (not including quotation
> > marks)
>
> Perhaps a fixed version of pmcom could be uploaded to the DJGPP FTP
> site.
If I recall back when we did this we found some references to a 1.1
beta that was available by request, so figured this would be handled
subsequently. Not sure where that stands currently.
-- David
- Raw text -