Arrrr, memories of TopSpeed Modula2, arrrrrrr

The compilation time for building the edited modules is well within my frustration threshold for C, as I said once all the transfers and executes take place I dont think theres a major difference (at least for incremental).

You are right about thinking about what you code before building and not waiting for the compiler to catch your mistakes.

Its good mind training to walk through modules and code blocks with a virtual debugger tracking the expected values and saying to yourself "this may fail if that fails", "wtf thats not meant to happen" etc.

I use Jalimo in eclipse in my windows laptop to build application for my IT and do the transfer using WinSCP. When I tried packaging my application I could only find the tutorial which was using scratchbox. So, I download andLinux, scratchbox and maemo SDK 4.0.1 but in the end the graphical interface which should show up seemed to be not how it should be. So, I'm in chaos. Should I stick to jalimo or it worth reinstalling andLinux and all in my windows laptop. Btw, what difference does it make? Plus I've no knowledge of C, C# and only little C++. Java is my main programming language. Thanks

Jalimo is still a little under development for main application development. In particular, one of the example SWT apps uses 90% CPU when just sitting there doing /nothing/.

Once that's fixed, I'm sure usage will take off and using non-Linux systems to build deb files (and source packages for the autobuilder) will become a lot easier/documented.

Help me out here - is C particularly difficult to learn? I've done a fair bit using PHP and Perl for web and Visual basic on Windows.
If not, which flavour of C?