silveira neto said:
First, thanks for the atention.
Sorry for my faults in the program, I learned C the day before.
IMO nobody can learn C in a day. I've been using C for
about 16 years, but I would not claim to be an 'expert' with it.
I'd only go so far to say I'm more or less 'comfortable' or
'conversant' with it (but not with many of it's 'dark corners'
-- i.e. obscure, less often used features).
And sorry for some words in portuguese, my live in Brazil, I forget
translate in the source.
Not a problem.
So, I think is important the portability of the source.
It can be important in many cases, yes.
I would know where I can learn about the C that I can write to all
plataforms, if this is possible.
It is possible. Learn how from good books.
See
www.accu.org for peer reviews by the experts.
What C is this C that we are talking about?
The language which is the topic of comp.lang.c is the standard
C language as defined by the international standard ISO/IEC 9899.
I compiled the remaked program, thanks Peter Nilsson, but as Robert
Tisdale, I dont liked the graphics. Maybe there is another way to do this
program portable and cool.
Standard C does not support graphics. But graphics can indeed be
done by applying a specialized library to a C program. However,
this will necessarily limit its portability (to those platforms
where the special library has been implemented). One example of
such a 'multi-platform-capable' library is 'wxWindows'.
Nonportable code isn't 'bad' per se, sometimes it's the only way
to do what you need. But I (and many others) still recommend that
as much of a C program as possible be written portably, and that
the platform-specific portions be clearly identified and separated
into their own modules. This will make porting less cumbersome.
HTH,
-Mike