Mail Archives: djgpp/2012/05/17/15:03:33
Well, I guess it sucks to send a book to the printing press with missing code.
The header and utility file in question were needed in every other example from
chap8 on... I will assume this is why they put out the second edition which I
got for $1.97 + $4.00 shipping, source code included. I'm sure with another
hour or two of review and tracking down the missing declarations, I could have
filled the code gap. I crossed checked both books with the source code, and
there are still differences it what is in the second book.
I know this is boring, but it is a reminder that things accidentally get left
out. Maybe too many people involved in preparing the source code for
publication.
Oh well, it's a good book even though... Good Xlib programming examples.
On Wednesday, May 09, 2012 12:02:52 AM you wrote:
> > Date: Tue, 08 May 2012 23:42:54 -0500
> > From: "John Wright" <john AT wacontrols DOT com>
> >
> >
> > I cannot track down the compile problem in this program. The program
> > demonstrates how to setup an event handler context management structure
> > to better manage event handling for multiple child windows. The problem
> > seems to be related to the local header file "xwins.h" which has a
> > #ifndef #else declarations. This program is a continuation of a previous
> > example that compiles fine. Most of the compile errors are related to
> > undeclared structure members. Storage is not being allocated in some
> > way?? I'm sure this is simple, but I just can't see it.
> >
> > Eventually, I want to port and compile some of these examples using DJGPP
> > V1.12 and Xlib200 stuff.
> >
> > This is X11R3 code. I'm compiling with gcc 2.7.2.3 using RedHat 6.22. I
> > included xctest.tar.gz. If it gets excluded from this, then I will be
> > glad to forward to whoever is interested in helping me with this
> > problem. The "xwin.h" and compiler error messages are not too long, so I
> > can post them if it is necessary.
>
> It got excluded. If DJ can figure out why and fix that (if it's some
> problem, as opposed to expected behavior), then fine. Otherwise, can
> you upload it to some public file uploading site out there and post
> here a link to that place?
- Raw text -