1 |
On Thursday 28 September 2006 14:16, Barry.SCHWARTZ@×××××××××××××.org wrote |
2 |
about 'Re: [gentoo-amd64] First Impressions': |
3 |
> "Boyd Stephen Smith Jr." <bss03@××××××××××.net> skribis: |
4 |
> > It's wrong-headed to deride or discourage users for using the features |
5 |
> > of their compiler when those functions are not erroneous. Instead, |
6 |
> > you should be leaning on the developers to fix the erroneous code. |
7 |
> |
8 |
> This looks like a false dichotomy to me. |
9 |
|
10 |
But, it's not. A piece of code it either conforms to a C/C++ standard the |
11 |
compiler implements or not. This may be hard to determine but, it is a |
12 |
statement that is either true or false, absolutely. |
13 |
|
14 |
If the code does not conform to the standard, the output of the compiler is |
15 |
undefined. In particular, it is acceptable for the compiler produce |
16 |
errors or produce a binary that crashes. The fault is with the code. |
17 |
|
18 |
If the code does conform to the standard, the behavior of the output of the |
19 |
compiler is specified. In particular, subject to resource limitations and |
20 |
hardware failure, the compile job must succeed and produce a binary that, |
21 |
again subject to resources and hardware, does not crash and performs the |
22 |
operations described in the source code. The fault is with the compiler. |
23 |
|
24 |
-- |
25 |
"If there's one thing we've established over the years, |
26 |
it's that the vast majority of our users don't have the slightest |
27 |
clue what's best for them in terms of package stability." |
28 |
-- Gentoo Developer Ciaran McCreesh |