0-9999 counter with c

During the time that guy/gal is being tested out, someone is allocated as mentor, and after the first day starting to climb the walls. The mentor is probably someone the company relies on, so having him/her go nuts doesn't help the morale or efficiency of the RD department.

At the same time, that junior did get some type of job to do. That job will not be finished unless someone else spends extra time doing it besides the ordinary assignments. Or maybe it will get finished, but have so bad quality that it is a disaster. But management comments that it can't really be that bad - just ship it and we fix any bug reports in due time.

And the bad outcome of the experiment may make the company wary of trying out yet another potential fool, in which case the resident staff will have to continue with their overload for even longer. When the company finally gets someone worth keeping, it is already too late. The company has already grown enough that they would have needed two new developers. But having just received one new developer, marketing et al can't see why RD are complaining about being overworked since they just got a new guy.

During the time that guy/gal is being tested out, someone is allocated as mentor, and after the first day starting to climb the walls. The mentor is probably someone the company relies on, so having him/her go nuts doesn't help the morale or efficiency of the RD department.

At the same time, that junior did get some type of job to do. That job will not be finished unless someone else spends extra time doing it besides the ordinary assignments. Or maybe it will get finished, but have so bad quality that it is a disaster. But management comments that it can't really be that bad - just ship it and we fix any bug reports in due time.

And the bad outcome of the experiment may make the company wary of trying out yet another potential fool, in which case the resident staff will have to continue with their overload for even longer. When the company finally gets someone worth keeping, it is already too late. The company has already grown enough that they would have needed two new developers. But having just received one new developer, marketing et al can't see why RD are complaining about being overworked since they just got a new guy.

let's give him the code for a counter from 1..9 *smile*

But lets make it designed with four discrete 1-bit variables ;)

can u make a counter for 0-9999 with c ?
line 4 people up representing each digit and have #1 wiggle the fingers, when he has wiggled all fingers, then #2 wiggles one.

Erik

> Then he gets a job somewhere and the real-world finds out he knows nothing. <

Well, if he gets a job somewhere, then the real-world will not find out he knows nothing. The one who finds out he knows nothing, will soon be punished, for the finding.

i got sum code .here it is when u need it.

for ( i = 0 ; i != 9999 ; i = i + one )

;

i = 9999 ;

Hallelujah !

"i got sum code .here it is when u need it."

Thanks for sharing with us.

Complex, yet beautiful in its simplicity. Pure genius.

On one hand, you haven't defined "one". On the other hand - would "one" be allowed to be given any value, or might your little counter possibly get into troubles for some values for "one"?

If you intend "one" to always be the value 1, why would you create a named variable or constant "one"? That is about as clever as creating a variable for pi named m3_1415926535. Having a constant with the same name as the value normally don't help, with a few exceptions. Having a constant is something you do to not have to remember the actual value, or to allow the constant to be changed. But as already mentioned - would it be allowed to change "one" to another value and would some values be unsafe?

Is there a reason for both having a loop and a direct assign of i = 9999?

And what is the data type for i?

By the way - did you post the code to have us check it out, or to help others who wants to know how to create a counter that counts to 9999?

> i got sum code .here it is when u need it.
>
> for ( i = 0 ; i != 9999 ; i = i + one )
>
> ;
>
> i = 9999 ;

I have a quicker solution:

int i=0;
while(i++<9999);

or, the hard way:

int *i=(int *) malloc(sizeof(int));

memset(i, 0, sizeof(int));

while(*i++<9999);

or ... after reading your code ... a much quicker solution:

int i = 9999;

*smile*

BR,
/th.

int i=0;
while( i++ < 9999 );

Although the source code may be briefer, it is rather unlikely that the generated machine code will be any different at all...

*pssschhhht* ...he doesn't know that! ;-)

Since we're now giving him the answers, here's the one I was going to suggest:

#define TWO 1

  ...

  int i;

  i = 0;

loop:

  i = i + TWO;

  if (i > 9999)
    goto end;

  goto loop;

end:

  ...

whoops ...

#define Z      0
#define N   9999
#define F    for
#define I    int
#define B  break
#define C     if

I i=Z;
F(;;) C(i++>N) B;

:-)

wtf?
www.linkedin.com/.../b06

/*
**======================================================================
**      My_Counter
**======================================================================
**
**  Counts to MAX_COUNT and returns the MAX_COUNT value.
**
**----------------------------------------------------------------------
**
**  Parameters Passed:      <void>
**  Parameters Returned:    u16 -- the counted value
**  Notes:
**
**          'ramble( )' expands to 9999 words of boredom.
**
**----------------------------------------------------------------------
*/
u16 My_Counter( void )
{
    ramble( 9999 ); // lots of comments
}

--Cpt. Vince Foster
2nd Cannon Place
Fort Marcy Park, VA