Date: Sun, 9 Feb 2003 08:05:28 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: djgpp AT delorie DOT com Subject: Re: GCC warning - incompatible pointer type In-Reply-To: <6ti1a.7694$kz5.871910@news1.east.cox.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sun, 9 Feb 2003, Jason Kircher wrote: > Of course, those examples have custom > comparison functions written in the example. Nothing using the standard > string comparison functions given in , which I used. I think you didn't look into the examples well enough. The following comparison function from the example _does_ use `strcmp', and that is how you are supposed to use `qsort' in your case without getting warnings: int qsort_stringlist(const void *e1, const void *e2) { return strcmp(*(char **)e1, *(char **)e2); } In other words, you need to write an interface function that casts the arguments and calls `strcmp'. > Of course, info is a pain to use... Only if you didn't take a few minutes to study it, which is highly recommended. It has superior methods of finding things quickly that will blow any Web browser out of the water. If you want a more graphic UI to Info, read section 5.1 of the DJGPP FAQ list, it mentions several Info readers with a more familiar UI. > Is there a program that can convert texinfo files into HTML files - > usable by lynx? I'd love to do that to ALL of the texinfo files. :D Get the *d.zip files for every package you downloaded, the docs formatted as HTML are already there. But I urge you to invest a little more time in learning Info, since it will let you find things much more efficiently. For starters, read the section about Info in the README.1ST file. HTML format doesn't give you the index search or the TAB-completion on available topics, two of the more important features of Info.