Re: [hpoj-devel] new "ptal-mlcd" I/O driver checked into CVS

[<pa...@rc...>]

Joe Piolunek wrote:
> The build fails with this output:
> ...
> gcc -I/home/joe/hpoj_proj/CVS/hpoj_CVS_03-10-2001/mlcd 
> -I/home/joe/hpoj_proj/CVS/hpoj_CVS_03-10-2001/mlcd/transport -O -g -Wall 
> -DEX_TRANSPORT_UNIX_PORT -DPAR_PLATFORM_LINUX -DUSB_PLATFORM_NONE -DJD_DEBUG 
> -c -o ExMgr.o ExMgr.cpp
> In file included from 
> /home/joe/hpoj_proj/CVS/hpoj_CVS_03-10-2001/mlcd/ParPort.h:396,
>                  from ExMgr.cpp:1981:
> /usr/include/sys/io.h: In function `void outb(unsigned char, short unsigned 
> int)':
> /usr/include/sys/io.h:98: parse error before `::'
Hi, Joe.  Thanks for the bug report.  I just checked in a change to ParPort.h
to wrap "#include <sys/io.h>" with 'extern "C" { }'.  Try it again after
doing a "cvs update" and see if that fixes the problem.  Perhaps I should go
through and do this around most if not all #includes from C++ files, just to
be on the safe side.

> Can you hold off on checking in the patch I posted recently? I only sent it 
> so you could look at the changes if you wanted to, and see if they work 
> correctly.
> 
> I'd like to modify some of the comments a little more to enable (but not 
> necessarily include) document generation by Doxygen or a similar utility, so 
> there will be at least one more patch, probably applied against the last 
> official release (0.7).
I haven't had a chance to try it out since I pretty much pulled the rug out
from under it by removing ojlib, but I'll wait for your next drop and build
it with 0.7.

> Generated documentation can be a benefit. Would it be a good idea for the 
> entire project?
It might be a good idea for PTAL at least, since other applications need to
be able to interface with it.  I don't know if it's necessary to generate
separate documentation for individual components that don't export their own
interfaces, but of course, it doesn't hurt to have the information in there
one way or another.

David