[Numpy-discussion] Toward a numpy build with warning: handling unused variable
Tue Aug 5 09:10:38 CDT 2008
Of course, you could also call GCC like this '-Wall
-Wno-unused-parameter'. Then you will only get warnings about unused
functions and local variables.
On Tue, Aug 5, 2008 at 9:49 AM, Charles R Harris
> On Tue, Aug 5, 2008 at 4:28 AM, David Cournapeau <firstname.lastname@example.org> wrote:
>> On Tue, Aug 5, 2008 at 1:29 AM, Lisandro Dalcin <email@example.com> wrote:
>> > David, I second your approach. Furthermore, look how SWIG handles
>> > this, it is very similar to your proposal. The difference is that SWIG
>> > uses SWIGUNUSED for some autogenerated functions. Furthermore, it
>> > seems the SWIG developers protected the generated code taking into
>> > account GCC versions ;-) and the C++ case, and also Intel compilers.
>> Yes, I would have been surprised if most compilers do not have a way
>> to deal with that. I did not know icc handled __attribute__.
>> Charles, are you still have strongly against this, since this is in
>> the vein of what you suggested (tagging the argument) ?
> I think tagging the argument is the way to go.
> Numpy-discussion mailing list
Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC)
Instituto de Desarrollo Tecnológico para la Industria Química (INTEC)
Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET)
PTLC - Güemes 3450, (3000) Santa Fe, Argentina
More information about the Numpy-discussion