Re: code portability
- From: Chris Dollin <chris.dollin@xxxxxx>
- Date: Thu, 10 Aug 2006 15:03:14 +0100
Frederick Gotham wrote:
Chris Dollin posted:
So I can't cook well if I don't work as a chef?
You won't get so much feedback as to the success of your recipes
if you cook only for yourself.
Yes, but I have my own sense of judgement.
It either tastes good or it doesn't.
/To you/.
It either runs fast and without crashing, or it doesn't.
It's either maintainable or it isn't.
If you have never worked in the industry nor have
had to satisfy a customer or their requirements I don't see how you can
make judgements on your style vs. what the undoubted experts here in
this forum promote.
I cook my own food to satisfy myself.
I write my own code to satisfy myself.
Then why are you wasting time trying to convince people that they
should like /your/ food? If you're coding for yourself, code for
yourself - our preferences shouldn't matter to you.
I'm not trying to convice people to start writing:
int const static *Func(void);
Just as well.
But rather to explain to them that it's a perfectly acceptable variant.
But it /isn't/. And the proof is, it's not being accepted. You keep
saying that it's perfectly acceptable, look, the grammar allows it
and you /can/ read it, see! and it's just like trying to convince me
that broccoli or liver tastes /nice/, ugh spit.
You're saying that you-all could get used to something different. We-all
are saying "what's the return on investment?". Since there isn't one,
I'm surprised you're surprised that people aren't interested in making
the effort.
"The grammar allows it" isn't enough. The grammar [including the lexis]
allows `int djh908gf( void *ewjh8455534 );` too, and `int *a, b;`,
and unrestrained use of `goto`, and redundant `auto`s and irrelevant
`register`s and pointless casts. The point about a widely-used ordering
for the formally order-irrelevant parts of a declaration means that
we don't have to /care/.
--
Chris "seeker" Dollin
Meaning precedes definition.
.
- Follow-Ups:
- Re: code portability
- From: Al Balmer
- Re: code portability
- From: Frederick Gotham
- Re: code portability
- References:
- code portability
- From: Eigenvector
- Re: code portability
- From: websnarf
- Re: code portability
- From: Malcolm
- Re: code portability
- From: Keith Thompson
- Re: code portability
- From: Richard Heathfield
- Re: code portability
- From: Keith Thompson
- Re: code portability
- From: Ian Collins
- Re: code portability
- From: Frederick Gotham
- Re: code portability
- From: Frederick Gotham
- Re: code portability
- From: Keith Thompson
- Re: code portability
- From: Frederick Gotham
- Re: code portability
- From: Keith Thompson
- Re: code portability
- From: Frederick Gotham
- Re: code portability
- From: Philip Potter
- Re: code portability
- From: Frederick Gotham
- Re: code portability
- From: Eigenvector
- Re: code portability
- From: Frederick Gotham
- Re: code portability
- From: Eigenvector
- Re: code portability
- From: Frederick Gotham
- Re: code portability
- From: Chris Dollin
- Re: code portability
- From: Frederick Gotham
- code portability
- Prev by Date: Re: TDD doesn't suck
- Next by Date: Re: TDD doesn't suck
- Previous by thread: Re: code portability
- Next by thread: Re: code portability
- Index(es):
Relevant Pages
|