Re: subroutine stack and C machine model
- From: spinoza1111 <spinoza1111@xxxxxxxxx>
- Date: Tue, 17 Nov 2009 08:30:58 -0800 (PST)
On Nov 17, 1:26 am, "Dennis \(Icarus\)" <nojunkm...@xxxxxxxxxxxx>
wrote:
"spinoza1111" <spinoza1...@xxxxxxxxx> wrote in message
news:aaa9dcf0-a312-405f-881e-b1d2282ee348@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Nov 16, 7:18 pm, "Dennis \(Icarus\)" <nojunkm...@xxxxxxxxxxxx>
wrote:
"Hektor Rottweiler" <spinoza1...@xxxxxxxxx> wrote in message
news:b865ca68-4733-47ec-ba76-84dcb2604eb6@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Nov 15, 9:04 pm, "Dennis \(Icarus\)" <nojunkm...@xxxxxxxxxxxx>
wrote:
"Richard Heathfield" <r...@xxxxxxxxxxxxxxx> wrote in message
<snip>
It seems to me that in order to be able to determine whether a
statement is true or false, you first have to understand it.
I think you've got it.
Thanks. Looks likespinoza1111may well be getting it too.
No, you're wrong. A careful writer would not call a text "clear" if he
thought it full of errors.
Then the careful writer should not publish it until the errors are
corrected.
If it's not clear, then you really can't assess whether errors are present
or not.
If it's not clear they probably are.
But Seebach was the careless writer, and his carelessness, unlike any
carelessness on Schildt's part, caused provable harm to a person.
Seebach labels as errors matters of taste and style. For example,
Seebach claims that the use of upper case on an obviously case-
insensitive file system is an error, and it's not.
It is an error, as has been previously explained.
No, it's not. If the code works as intended on a Microsoft platform
and that platform is case-insensitive, the code is correct if it was
intended to run that platform.
Very few Microsoft C coders intend their code to run on non-Microsoft
platforms. If they were to want to write a portable program, they
wouldn't use C, because no matter what style C is written-in, the code
is not portable because it takes line by line analysis to make sure it
will run on a new platform, C being both "low level" and a series of
stupid errors in language design (of which making file identifiers
into Holy Writ is one of the stupidest and most ugly).
Microsoft coders have truly portable languages which don't even
require Windows because as we know .Net is portable as well.
Non-MS coders if they are professionals use Java and not C. If
efficiency is an issue they use best of breed algorithms and tune for
the most common cases and within the most frequently used code
pathways.
<snip>
Dennis- Hide quoted text -
- Show quoted text -
.
- References:
- Re: subroutine stack and C machine model
- From: Seebs
- Re: subroutine stack and C machine model
- From: spinoza1111
- Re: subroutine stack and C machine model
- From: Nick Keighley
- Re: subroutine stack and C machine model
- From: spinoza1111
- Re: subroutine stack and C machine model
- From: Richard Heathfield
- Re: subroutine stack and C machine model
- From: spinoza1111
- Re: subroutine stack and C machine model
- From: Richard Heathfield
- Re: subroutine stack and C machine model
- From: Dennis \(Icarus\)
- Re: subroutine stack and C machine model
- From: Richard Heathfield
- Re: subroutine stack and C machine model
- From: Dennis \(Icarus\)
- Re: subroutine stack and C machine model
- From: Hektor Rottweiler
- Re: subroutine stack and C machine model
- From: Dennis \(Icarus\)
- Re: subroutine stack and C machine model
- From: spinoza1111
- Re: subroutine stack and C machine model
- From: Dennis \(Icarus\)
- Re: subroutine stack and C machine model
- Prev by Date: [OT] cross-compile tutorial
- Next by Date: Macro counting invocations
- Previous by thread: Re: subroutine stack and C machine model
- Next by thread: Re: subroutine stack and C machine model
- Index(es):
Relevant Pages
|