Re: Pointers to "why C behaves like that ?"

  "jacob navia" <jacob@jacob.remcomp.fr> wrote:
> void updateAccount(newAmount)
> {
> CurrentAmount = ReadCurrentAccount(database);
> CurrentAmunt =CurentAmount+newAmount;
> StoreDatabase(CurrentAmount);
> }
>
> You see the problem?
>
> A typo in the spelling of the variable "CurrentAmunt" in line 2
> creates a new variable "CurrentAmunt" that receives the result of the
> addition. Since the CurrentAmount variable is stored, the account
> receives a wrong value, and there is NO WAY to spot this bug until
> runtime!
>
> This means that any error when writing down the name of a variable is
> a fatal error that will never be spotted. C prevents this by requiring
> you to explicitly state the names you want at least twice!


So a language that allows you to drop declarations lets you save five
seconds because you don't have to type "long" or "int" or whatever in
two places, and then it costs you three hours to find the bug.


It is much better if I can specify redundantly what the code is
supposed to do; that makes it more self-documenting and it is more
likely that the code doesn't compile if I make mistakes.

Return to the comp.compilers page.
Search the comp.compilers archives again.