Thread: Compiler error i dont understand

You are calling "moveDown" before you define the function, which means that the compiler "guesses" what the function looks like, and then decides "Huh, that's not what I expected".

Either move the function up above the call, or declare a prototype.

And enable warnings in your compiler, so that the compiler tells you that there is a missing prototype.

--
Mats

You should learn to indent first: http://cpwiki.sf.net/User:Elysia/Indentation
And then you could start giving all functions an explicit return type.
Then you could get rid of those nasty global variables.

Originally Posted by mushy

... Any ideas how i could build on this program to make it more advanced?

Originally Posted by Elysia

You should learn to indent first: http://cpwiki.sf.net/User:Elysia/Indentation
And then you could start giving all functions an explicit return type.
Then you could get rid of those nasty global variables.

It tickles me that the more basic you get the more advanced the code becomes.

Originally Posted by mushy

i appreciate your help and all elysia. However i'd appreciate if you would take that snobby attitude out of your replys. Yea your the programming master, way better than me . But perhaps if you want, we can discuss quantum mechanics or play a game of checkers of which i was the best player in my country for two years. Mabye we can talk about nuclear fusion or how neutron stars are produced.

You asked for suggestions, I gave you some.

You see, your life if programming. Its all you have.

That's not true. I may be a programming "master", but that's because it's fun and I have lots of experience. Of course I do other things as well.

However if you were to ask me about the countless things im better than you at, i'd tell you in a polite way and give you the respect you deserve. I think you need to adjust your attitude and rethink your outlook on life.

That's so funny because you really have no idea who I am.
I should politely say that it is not good to guess. I don't ask what you do, you don't ask what I do and we do not guess, foremost of all!
I gave you suggestions.
You don't like them? Then you can politely decline. I can't force you.

so to answer your question. My indentation is fine. Its readable your just being a picky for no reason other than to give a sarcastic answer to a question which you realised was asking for something else.

It's not. Some places, it's a mess. Ask anyone at the board and they'll tell you the same.
Indentation is not a toy. It's a way to make your less prone to bugs and more readable to others. It's just as important as writing safe code.

I realise by having a go at you, im ruining my chances of anyone else ever helping me on here again. But if feel like that i dont want their help, because anyone who holds you in high regard clearly isnt worth knowing.

Careful here. That's big words.
If you are unhappy about one individual, don't make everyone an enemy to you.

Not that anything i say will have an effect on you. After all what do you expect from a pig but a runt!

So what we get from helping you is rude remarks? Perhaps you should go try to teach yourself and we stop helping you.

I have helped countless others. Many like you. Many have expressed thanks for my and others help. Why should you be an exception? I'm open to listening to what other people think and know, and you should too.

I don't always agree with Elysia, nor do I mind other people disagreeing [and we certainly don't have exactly the same rules about indentation style], but I do agree that indentation should be consistent and that it's part of how you make your code readable to another person.

Your code happens to be fairly inconsistent: The openign bracket for functions is sometimes on the same line as the function, and sometimes not. End braces for loops and if-statements are a bit hit-and-miss about whether the line up with anything at all, never mind lining up with the "thing" they belong to.

And the fucntion "moveup" doesn't have a return type declaration.

Using global variables is seen as quite a bad thing by most people [although we all do sometimes - but the coding style at work almost requires permission from the Pope to get a global variable in the code]. In this particular case, there is no particular good reason to do so - you could quite easily use local variables and pass arguments from one function to another.

No I don't know that much about quantum mechanics, but I probably know more about the fishes in the Family of Loricariidae than most people on this forum [although I don't do that for a living]. Nor can I play checkers, I'd probably loose even against a 5-year old, because it's a game I have never learnt [I could probably learn it, but it's not a traditonal game in Sweden where I grew up, and I'm not sure it is played regularly in England where I live, so I don't quite know who I would ask about it].

We all know different things, and that's often helpful on a forum like this, because that's how you learn more about things. If we all knew the same thing, then we wouldn't have anything to discuss, and no hope in learning new things from others.

--
Mats

Here's something that does something that you seem to be looking for (going from point A to B if there are no obstacles).

It treats X and Y axis separately and the strategy for both is the same and very simple (implemented in approach): if value and target are not equal increment or decrement by one to make it closer to the target.

Note the use of function arguments over global variables.

Code:

#include<stdio.h>

int approach(int from, int to)
{
    int newPos = from;
    if (from < to) {
        ++newPos;
    }
    else if (to < from) {
        --newPos;
    }
    return newPos;
}

void plotRoute(int startX, int startY, int endX, int endY)
{
    printf("From [&#37;d, %d] to [%d, %d]\n", startX, startY, endX, endY);
    printf("[%d, %d]\n", startX, startY);
    while (startX != endX || startY != endY) {
        startX = approach(startX, endX);
        startY = approach(startY, endY);
        printf("[%d, %d]\n", startX, startY);
    }
}

int main()
{
    plotRoute(0, 0, 4, 3);
}