On Tue, Jun 17, 2003 at 01:53:55PM -0600, D. Stimits wrote:
>I found something interesting, on a debug compile. How is the file
>llib-lncurses used? Using the most recent roll-up patch 20030510, and
systems that provide the "lint" program can use that to build a
lint-library.
I don't use it much for that anymore - only Sun seems to deliver a
quasi-working
lint currently - but it's useful for a snapshot of the interfaces provided
by the library. Most of the file is generated using cproto (there're a
few lines that I edit by hand).
>comparing this file from one I did a debug build on a couple months ago,
>I see that the newest one has const on fmt, but the debug version does
>not (I am not currently linking against the debug version, but the rpm
>for the binary was created from it). That llib-lncurses file seems to be
>the key, as on the older one it has this:
>#undef mvprintw
>int mvprintw(
> int y,
> int x,
> char *fmt,
> ...)
> { return(*(int *)0); }
>
>On this older one it removes the const version and puts non-const back
>in. I guess what I need is a new rpm based on all of the patches that
>have been out since 5.3, rather than one based on only part of the
patches.
I should put an rcs identifier in that file (just so we could agree on
which
one you're looking at). Mine was last touched April 12. The previous
version was from August 31. The current one has const's for printw
because
of the change I made in November.