[OT:]
I think a sort of perma-link to the latest update would be fine for all us beta developers, working for nothing...
[/OT]

My guess is that Dick and the other developers wake up in a sweat every morning, wondering if you've created yet another piece of code that kills the compiler!

Regards,
Xander

RobotC has come a long way since the 1.0 version. I am just grateful that I have RobotC to work with. Of course, it has its down side, but the upside surpass the down side..... Small footprint, very very low cost, no big complaint. At least, not like some other software I have used, a newer version broke something else. Then, refixing it ends up unfix something else!!!

back to the pointer/structure issue: it will be great also include more standard C pointer to structure access...

e.g.

I agree to this - above all if it included more standard C altogether

But back to the pointers:
Pointers on the whole only would work like in standard C, if there was a heap to allocate dynamic memory by pointers.
Cause this ain't possible because of the Lego memory design ( if I understood Dick correctly), this unfortunately will never happen.
On the other hand, some features of C++ are included in RobotC (e.g., structures, function call by reference, overloading of functions), which don't have their place in ANSI C (C99), whereas related ANSI C features and many other things (e.g., 7-dimensional arrays, pointers as function parameters, standard I/O, libraries, recursive functions...) are completely missing.
This unfortunately leads to sort of unsystematical appearance.