Search:

Aha, so its only the definitions in .h files that are "exposed" to main.c?
Actually, that makes a lot of sense because I wanted to remove direct access to the structs members directly... Using an...

Just trying to figure out why I would need to define struct point a second time in main.c in order to remove the dereferencing pointer to incomplete type error I am having in main.c?

Am I tackling...

But check out what Arduino is doing to your code, it translates it to this:

#include <Arduino.h>


// Declared weak in Arduino.h to allow user redefinitions.
int atexit(void (* /*func*/ )()) {...

I think checking if
turno!='g' in the second scanf block is redundant since there is no way the code can reach that point if indeed turno is 'g'.

I seen something like this in Advanced Linux Programming Book . It recommends not to modify environ directly (you haven't) but use setenv and unsetenv functions instead, think the reasons are pretty...

Yeah I never use it, I just seen it in some book I was glancing over and thought it was interesting.

There is actually another paramater you can stick into int main()...
Atleast this works on Linux not sure about other systems...



#include <stdio.h>

Yeah I got a bit side tracked playing with pointers, it's a ridiculous concept reassigning a const! :redface: thats what variables are for :D

Ok so I'm playing around learning about pointers and came across something a bit head scratchy with the static keyword...



int main(int argc, char* argv[]){
int *ip;
static const int FIVE;
...