C programming: working with pointers

[chroot]

Math Is Hard,

The assignment seemed to specifically ask for pointer incrementing, like this:

void copy_ptr(double *ar1,double *ar2,int n)
{
   int i;
   for(i=0;i<n;i++)
      *(ar2++) = *(ar1++);
}

 

[Math Is Hard]

php tags

I am SO loving this! Yeah - I just went back and indented and it was so EASY!

 

[Math Is Hard]

Math Is Hard,

The assignment seemed to specifically ask for pointer incrementing, like this:

void copy_ptr(double *ar1,double *ar2,int n)
{
   int i;
   for(i=0;i<n;i++)
      *(ar2++) = *(ar1++);
}

oops! sorry- I think I got carried away with the formatting fun stuff! so, I should use ++ for "pointer incrementing"?
using + i won't move to the correct position in the array?

 

[chroot]

Math Is Hard,

Remember the three qualities of a good programmer:

1) Laziness. No one should have to do much work, so a good programmer should strive to make the user's life utterly push-button easy.

2) Impatience. No one should ever have to wait for a computer to do anything, so programmers should be careful with their algorithm designs to make sure their users never have to wait for anything.

3) Hubris. Programmers should take excessive pride in their work, and should strive to make every program they write complete, totally functional, and elegant.

The PHP tags are really an example of some programmer on the vBulletin team demonstrating quality number one.

- Warren

 

[chroot]

oops! sorry- I think I got carried away with the formatting fun stuff! so, I should use ++ for "pointer incrementing"?
using + i won't move to the correct position in the array?

Your code using pointer arithmetic (the + signs) will certainly work, but it might not be the best way to meet the specification. The specification said to use pointer incrementing. Normally, I associate the ++ operator with the word "incrementing," but it may just be a semantic issue.

- Warren

 

[Math Is Hard]

Math Is Hard,

Remember the three qualities of a good programmer:

1) Laziness. No one should have to do much work, so a good programmer should strive to make the user's life utterly push-button easy.

2) Impatience. No one should ever have to wait for a computer to do anything, so programmers should be careful with their algorithm designs to make sure their users never have to wait for anything.

3) Hubris. Programmers should take excessive pride in their work, and should strive to make every program they write complete, totally functional, and elegant.

Wow - who knew?? I promise to try my best to acquire these ..uh.. virtues!

 

[Math Is Hard]

Normally, I associate the ++ operator with the word "incrementing," but it may just be a semantic issue.

That's good enough for me. I'll take your advice on that and use ++ in my final version.

 

[Math Is Hard]

Thanks, again!

 

[faust9]

Math Is Hard,

Remember the three qualities of a good programmer:

1) Laziness. No one should have to do much work, so a good programmer should strive to make the user's life utterly push-button easy.

2) Impatience. No one should ever have to wait for a computer to do anything, so programmers should be careful with their algorithm designs to make sure their users never have to wait for anything.

3) Hubris. Programmers should take excessive pride in their work, and should strive to make every program they write complete, totally functional, and elegant.

The PHP tags are really an example of some programmer on the vBulletin team demonstrating quality number one.

- Warren

You forgot 4)

4) Once you land a job as a programmer learn to obfuscate as much as possible so that you are the only programmer able to maintain certain chuncks of code thus ensuring job security.

 

[Math Is Hard]

You forgot 4)

4) Once you land a job as a programmer learn to obfuscate as much as possible so that you are the only programmer able to maintain certain chuncks of code thus ensuring job security.

OMG! I had a job once where ALL the programmers lived religiously by that guideline. Not even the tiniest cryptic comment was ever written. My job? To go around to the programmers and produce documentation on what they were coding. Since they all refused to document or comment my boss thought I should be the one to do it. He wanted to farm out some of the work overseas so he wanted to create a guidebook for these contracted developers who would write new modules of the app.
It was horrible. The programmers were really protective and defensive about showing anyone their code or explaining to anyone what it did.
And what a mess. By the time I came to work their the application was three fourths done and there was no formal spec - just shoe boxes full of meeting notes and emails from the client.

 

[robphy]

For more qualities, consult this enlightening article on good programming techniques:
How To Write Unmaintainable Code

 

[Math Is Hard]

For more qualities, consult this enlightening article on good programming techniques:
How To Write Unmaintainable Code

LOL! That's hilarious!

I love the quotes at the beginning of each section, especially thie one:

Quidquid latine dictum sit, altum sonatur.
Whatever is said in Latin sounds profound.