I want to learn MSX-C, where do I start?

Yeah Nestor is using SDCC, perhaps he could help some with this topic

About manual, it should be really apreciate to get translated MSX specific parts of the manual. This is, the standar commands are not relevant since you can use any standar C manual, but specific MSX functions not. Clearly it should be a valious msx.org wiki content

@ericb59 Wellcome to MSX-C, let's try our best

Yes, it's easy. Just define variables to point to a memory location. For example, from the COLOR.C sample program that comes with MSX-C:

#define FORCLR (*(TINY *)0xf3e9)   /* foreground color */
#define BAKCLR (*(TINY *)0xf3ea)   /* background color */
#define BDRCLR (*(TINY *)0xf3eb)   /* border color */

From this point on, you can refer to FORCLR, BAKCLR and BDRCLR as TINY variables (TINY is an 8-bit value in MSX-C), and these variables are located in memory addresses 0xF3E9, 0XF3EA and 0xF3EB, respectively. You can read/write these variables freely.

#define FORCLR (*(TINY *)0xf3e9)   /* foreground color */
#define BAKCLR (*(TINY *)0xf3ea)   /* background color */
#define BDRCLR (*(TINY *)0xf3eb)   /* border color */

Yes, these obey standard pointer arithmetic. In this example we have three pointers to TINY values, but they could have been pointers to, say, structs representing characters in a game, or bullets flying towards your ship...

Great input, thanks for the url. Let's see if a community of MSX-C programmers is created ;)

Please fight the babel.
The question is not only what C to use, but what C to write.
A C that every compiler is asked to translate.
Is that even more ado, no, I am actualy trying to make things easy.
But ROM, DOS, BASIC environment, one CP/M compiler vs SDCC, that alone makes six combinations of babel.

@AxelStone, you wanted to make a game, right?
maybe the "hello world" app for the MSX game coder should be this:

	di(); out(0x99, 15); out (0x99,128 + 7); ei();

it makes the border color 15. getting the machine to do something, some first feedback.
based on the out() that can do the vertical roll register and blitter command engine and everything,
on every compiler.

so the first thing an MSX C should have is to make the z80 available:

void di();
void ei();
void halt();

void out(char port, char n);
char in(char port);

void* otir(char port, unsigned char count, void *p); /*returnvalue must be the slided pointer*/
void* otir29(char port, unsigned char count, void *p); /*for MSX1 VDP , 29 cycles*/
void* inir(char port, unsigned char count, void *p);
void* inir29(char port, unsigned char count, void *p);

Let me know in case anywhere there is an in() out() that is specified different.
The otir() can be made based on out() when one has nothing else at hands.

when JaviLM has sprites based on vpoke(), when you got an out() then in 5 minutes you can get his vpoke.
"his" vpoke:
the exact function signature of vpoke() is not so clear,
e.g. how to handle the 128k vram vpoke on a 16bit 64k C.
things get easy when it is based on a compatible out().