Date: Mon, 26 Jul 1999 19:22:56 +0300 (IDT) From: Eli Zaretskii X-Sender: eliz AT is To: Rolf Campbell cc: djgpp AT delorie DOT com Subject: Re: Strange localtime function behaviour In-Reply-To: <379C738B.5FD0736F@americasm01.nt.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Mon, 26 Jul 1999, Rolf Campbell wrote: > What bugs have you found in Borland C/C++? I did notice a few automatic > variable allocation bugs (2 local variables would get the same location on the > stack occasionally). Is that not enough? How can you work with a compiler that cannot even manage its stack? I stopped counting their bugs 5 years ago, after I submitted a detailed bug report about their implementation of alloca and never heard from them again. > I have found that it's compiler error messages are much less cryptic. Actually, I find GCC's diagnostics quite self-explanatory. What messages are unclear? > Also, I > liked the way Borland's help pages offered help on more than just function > calls. What else would you like to see in the docs of every function? > I have been meaning to try writing some info files for DJGPP that do > just that, but I don't know where I can get a good program for writing info > files. You don't write an Info file, you write a Texinfo file which is then converted into Info by the makeinfo program, as part of the library build procedure. makeinfo.exe is in the txi312b.zip package, and the docs in there include a complete description of the Texinfo language and a very good style guide. The best vehicle for writing a Texinfo document is (of course!) GNU Emacs, which has a special Texinfo mode. If you want to know how is DJGPP docs written, look at the *.txh files in djlsr202.zip, they should tell the whole story about the standard format used by our docs. Contributions should be sent to djgpp-workers AT delorie DOT com.