Thread: Static arrays and ellipsis

I'm pretty sure the "real" use case is for things like sparse matrices, since you still get the auto-fill-with-zeroes feature.

(EDIT: Oh, if you mean ellipses for macros, then I think that is new in 99 yes. I still have no idea where you're headed with templates, though.)

i was wrong about the templates... i glossed over the wikipedia and thought it was ALSO talking about plain old C (which i just took to be true, as there may be variants of C like that...) even though i've never seen any templates for C.

Originally Posted by quzah

I can't possibly think of a use for initializing only the end of an array.

Quzah.

alright.. well, what do you think of only initializing the start of the arrays??

look, i know a lot of you think in very "concrete" terms... if there are NO PREVIOUS EXAMPLE, then it CAN'T BE. you think in terms of that... instead of very concise solutions with huge implications. you think of very specific programs... sort of like your IT course lecturer telling you ok, write me this program and that does specifically this and that...

...and my babblings about standard this and standard THAT are just philosophical arguments meant to distract you or i' so thoroughly lost that i'm trying to get those other people lost too...

things that i bring up are no more than little tidbits that i can afford to throw away (without any disadvantage to me) in hopes that some bloke will pass that revision to the next amendment of C.

my bad, too you need these 2 to make it work:

new_inst_strm_stack.def:

Code:

/*  for the total memory alloced by stacks, as to what's most optimal is up to the client */
#ifndef INST_STRM_RESIZE_BUFFER
#define INST_STRM_RESIZE_BUFFER                       (400)
#endif

#ifndef INST_STRM_START_BUFFER
#define INST_STRM_START_BUFFER                        INST_STRM_RESIZE_BUFFER
#endif



#ifndef INST_STRM_PRAC_LIMIT
#define INST_STRM_PRAC_LIMIT                             (1000)
#endif




#ifndef INST_STRM_LEAVE_MEM_BUFFER
#define INST_STRM_LEAVE_MEM_BUFFER                (200)
#endif





#ifndef INST_STRM_STACK_ID
      #error "please specify id number"
#endif


#ifdef INST_STRM_NUM_STACK
      #if INST_STRM_STACK_ID >= INST_STRM_NUM_STACK
            #error "stack id exceeds id bounds"
      #endif
#endif

new_inst_strm_stack-break.def:

Code:

#undef INST_STRM_STACK_ID

and don't think this is even a 1/10th of the entirety of my project.

Originally Posted by quzah

You already can just initialize the start of an array. It's been in the standard forever. Anything you don't initialize is set to zero.

Code:

int foo[5] = { 1, 2 }; /* 0, 0, 0 are the last three */

Quzah.

EXACTLY!!! omfg you, mean, you didn't see this coming?? alright, i'll lay down to you simply so you understand me in detail.

well from my example above, you can clearly see that i traverse the arrays from highest place to the lowest... and the reason for that may be a variety of things... for my case it's because how CPU flag registers work in CISC... so it's very easy to see why it can be VERY advantageous to address the last elements.... in that manner, initializing the start of a static array is absolutely no different from initializing the last ones.