|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 17.08.2012 22:08, schrieb Le_Forgeron:
> Should the literal be extended with a "u" to make it happy ?
Yes.
> (only the 3 big ones)
Why not all of them?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 8/17/2012 4:17 PM, clipka wrote:
>> vfesession.cpp:594:11: warning: case label value is less than minimum
>> value for type [enabled by default]
>
> That line seems somewhat bogus.
Variable 'm_BackendState' is declared as type 'State' (vfe/vfesession.h
line 1316). The switch statement (vfe/vfesession.cpp line 576) contains
a 'case -1:'. Whoever wrote that code perhaps expected that
m_BackendState could have the value '-1'. If it does, then the case will
never be caught since '-1' is not a valid value for that enum.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 17.08.2012 23:35, schrieb Dave:
> On 8/17/2012 4:17 PM, clipka wrote:
>>> vfesession.cpp:594:11: warning: case label value is less than minimum
>>> value for type [enabled by default]
>>
>> That line seems somewhat bogus.
>
> Variable 'm_BackendState' is declared as type 'State' (vfe/vfesession.h
> line 1316). The switch statement (vfe/vfesession.cpp line 576) contains
> a 'case -1:'. Whoever wrote that code perhaps expected that
> m_BackendState could have the value '-1'. If it does, then the case will
> never be caught since '-1' is not a valid value for that enum.
Yes, that's what I'm thinking. Have done some quick code digging to see
if it is ever set to -1 somewhere, but it turns out to be more than a
5-minute job.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymousorg> wrote:
> Am 17.08.2012 19:53, schrieb Dave:
> > renderfrontend.cpp:1165:57: warning: trigraph ??) ignored, use
> > -trigraphs to enable [-Wtrigraphs]
>
> Trigraphs suck, but yes, we should avoid them.
Hard to believe there was a time when not all English-based computers understood
7-bit ASCII.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 18.08.2012 00:39, schrieb Cousin Ricky:
> clipka <ano### [at] anonymousorg> wrote:
>> Am 17.08.2012 19:53, schrieb Dave:
>>> renderfrontend.cpp:1165:57: warning: trigraph ??) ignored, use
>>> -trigraphs to enable [-Wtrigraphs]
>>
>> Trigraphs suck, but yes, we should avoid them.
>
> Hard to believe there was a time when not all English-based computers understood
> 7-bit ASCII.
Well, the trigraphs were there for /non/ English-based computers, which
often used 7-bit national derivatives of ASCII. Those typically replaced
a common set of 8 characters - curly braces, square brackets, pipe
symbol, backslash, tilde and hash - with language-specific characters
(in the German "GSCII", for instance, those were the umlauts, the sz
ligature, and the German paragraph sign), so C programs without
trigraphs would look pretty odd on those computers.
BTW, the UK also had their own derivative of ASCII, replacing the hash
sign with a pound sterling sign, but AFAIR the other characters were
left unharmed.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymousorg> wrote:
> (in the German "GSCII", for instance, those were the umlauts, the sz
> ligature, and the German paragraph sign),
Why does a German acronym begin with the letter 'G'?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 17/08/2012 23:19, clipka nous fit lire :
> Am 17.08.2012 22:08, schrieb Le_Forgeron:
>
>> Should the literal be extended with a "u" to make it happy ?
>
> Yes.
>
>> (only the 3 big ones)
>
> Why not all of them?
>
Your wish are my command.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 18.08.2012 03:05, schrieb Cousin Ricky:
> clipka <ano### [at] anonymousorg> wrote:
>> (in the German "GSCII", for instance, those were the umlauts, the sz
>> ligature, and the German paragraph sign),
>
> Why does a German acronym begin with the letter 'G'?
Because in this case it's a variation of an English acronym?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 17/08/2012 23:17, clipka nous fit lire :
>> renderfrontend.cpp:1165:57: warning: trigraph ??) ignored, use
>> -trigraphs to enable [-Wtrigraphs]
>
> Trigraphs suck, but yes, we should avoid them.
The issue with trigraph is that young coders do not know they might
indeed use them without knowing. Same would go for digraph, but the
pattern is less obvious for them.
Trigraph in C are started by a doube ?. So chess comments are dangerous
in C. ( ?? (blunder, in chess) ).
http://en.wikipedia.org/wiki/Digraphs_and_trigraphs
Here, trigraph happens with ??)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 8/17/2012 15:57, clipka wrote:
> Well, the trigraphs were there for /non/ English-based computers, which
> often used 7-bit national derivatives of ASCII.
Trigraphs were there for computers using EBCDIC, 6-bit bytes, and so on.
> Those typically replaced a
> common set of 8 characters - curly braces, square brackets, pipe symbol,
> backslash, tilde and hash - with language-specific characters (in the German
> "GSCII", for instance, those were the umlauts, the sz ligature, and the
> German paragraph sign), so C programs without trigraphs would look pretty
> odd on those computers.
Well, that too. But I think it was more for being able to code C on punched
cards than it was replacing umlauts with equally-unreadable trigraphs.
> BTW, the UK also had their own derivative of ASCII, replacing the hash sign
> with a pound sterling sign, but AFAIR the other characters were left unharmed.
That's why Americans sometimes call # the "pound sign".
--
Darren New, San Diego CA, USA (PST)
"They're the 1-800-#-GORILA of the telecom business."
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|