Re: 'static' : strange behavior

christian.bau <christian.bau@xxxxxxxxxxxxxxxxxx> wrote:

void init_this (void) {
static int anarray [10];
int i; for (i = 0; i <= 10; ++i) anarray [i] = 0;
}

Ahem. Surely I cannot be the only person to have noticed this
mistake, which explains everything...

Andrew,
.

References:
- 'static' : strange behavior
  - From: Mark
- Re: 'static' : strange behavior
  - From: Eric Sosman
- Re: 'static' : strange behavior
  - From: Mark
- Re: 'static' : strange behavior
  - From: christian.bau
- Re: 'static' : strange behavior
  - From: christian.bau

Relevant Pages

Re: const oddity in decorated names
... void foo ... void foo(int * const bar). ... since array names cannot be assigned to, it's making x const for decoration ... or is this just a mistake? ...
(microsoft.public.vc.language)
Re: References to functions ?
... > void wrote: ... except due to a mistake, why would one want to have ... external resource and is designed with RAII so the constructor allocates ... there is allways, of course, the case when my fun_object class is huge and I ...
(comp.lang.cpp)
Re: MS C++ :( - x64 - what about pointers?
... This technics is useful for data format out. ... void PrintSize ... Ahem... ...
(microsoft.public.vc.language)
Re: Whats wrong in my function of reverse the doubly linked list with dummy node.
... do-while would also repeat the same mistake. ... handle the ultimate case seperately as below: ... > void reverse_list ...
(comp.lang.c)
Re: auto_ptr: reassigning to member of owned object
... >> void main ... > obligatory - main must return int comment. ... My mistake. ...
(comp.lang.cpp)