[prev in list] [next in list] [prev in thread] [next in thread] 

List:       perl5-porters
Subject:    Re: Warnings with const char *const * arguments
From:       Yitzchak Scott-Thoennes <sthoenna () efn ! org>
Date:       2005-06-30 17:56:57
Message-ID: 20050630175657.GD3104 () efn ! org
[Download RAW message or body]

On Thu, Jun 30, 2005 at 11:22:46AM +0100, Steve Hay wrote:
> But what do you mean by "correctly"?  You seem to be meaning "what SUSv3 
> says", whereas I would have thought that "correct" for a given compiler 
> is "whatever that compiler's headers say".
> 
> You're right that it doesn't hurt (and doesn't warn) to apply the cast 
> in the VC++ case, i.e. make them "correct" in the SUSv3 sense, but the 
> cast is not required w.r.t. VC++'s own header files so it seems silly to 
> do the cast.

Ah, we've been talking past each other.

I was trying to say (and still think) that if you have to use ifdefs,
the case singled out should be the one that doesn't follow standards
and doesn't work with the standards-correct code.
[prev in list] [next in list] [prev in thread] [next in thread]