On 14 October 2012 13:38, Andreas Schwab wrote:
> Manuel López-Ibáñez writes:
>
>> aux-infoFILE /* we could accept this to be compatible with some
>> options like -B */
>
> Concatenated option arguments (without separators like '=' or '-')
> should only ever be used for single character options.
Manuel López-Ibáñez writes:
> aux-infoFILE /* we could accept this to be compatible with some
> options like -B */
Concatenated option arguments (without separators like '=' or '-')
should only ever be used for single character options.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Ke
On Sat, 13 Oct 2012, Manuel L?pez-Ib??ez wrote:
> OK. The attached patch implements this. Does the approach look ok? I
> will write changelog and more comments if it seems reasonable. One
Without the comments explaining the semantics of the new functions and
their parameters, I'm not going to at
On Sat, Oct 13, 2012 at 11:33 AM, Manuel López-Ibáñez
wrote:
>
> 1) Are references allowed now that C++ is the default?
I'm not sure we addressed those in the coding conventions. I would like to say:
1) const references are always fine;
2) non-const references as local variables are always fine
On 12 October 2012 17:18, Joseph S. Myers wrote:
> On Fri, 12 Oct 2012, Manuel López-Ibáñez wrote:
>
>> I am trying to encode the relationship between Wstrict-aliasing and
>> Wstrict-aliasing= in the .opt files, and the same for Wstrict-overflow
>> and Wstrict-overflow=. However, the parameters of
