From bug-octave-request at bevo dot che dot wisc dot edu Tue Nov 2 21:05:53 1999 Subject: Warnings compiling octave-2.1.19 with latest egcs snapshot From: "John W. Eaton" To: "Billinghurst, David (RTD)" Cc: "'bug-octave at bevo dot che dot wisc dot edu'" Date: Tue, 2 Nov 1999 21:05:21 -0600 (CST) On 3-Nov-1999, Billinghurst, David (RTD) wrote: | There were a few more warnings compiling octave-2.1.19 with latest | (19991025) egcs snapshot | | For various types - in this case Complex - we get | liboctave/DiagArray2.cc:93: warning: unused variable `Complex *bar' | and | liboctave/DiagArray2.cc:107: warning: unused variable `Complex *bar' | My C++ is not adequate to comment. OK, I fixed these, now that it is possible to say template T some_function () { return T (); } even for builtin types like double, int, etc. | Also need to #include for liboctave/getopt.c | liboctave/getopt.c: In function `_getopt_internal': | /liboctave/getopt.c:455: warning: implicit declaration of function | `strncmp' Hmm. The comments in that code say: /* We want to avoid inclusion of string.h with non-GNU libraries because there are many ways it can cause trouble. On some systems, it contains special magic macros that don't work in GCC. */ Perhaps it is best to just ignore this warning, which only occurs because Octave's Makefiles add -Wall to the compiler flags when gcc and g++ are used. How many packages do you know of that compile cleanly with -Wall? jwe --------------------------------------------------------------------- Octave is freely available under the terms of the GNU GPL. To ensure that development continues, see www.che.wisc.edu/octave/giftform.html Instructions for unsubscribing: www.che.wisc.edu/octave/archive.html ---------------------------------------------------------------------