(^_^) i'd say both rich and van have good advice there ...
comming from C++ you can probably understand the modular development better than a newbie to programming.
Now whilst you can't persay create an actual object which you can link to something - the underlaying principals from creating an object and classes are already right there infront of you.
I'd suggest you take in the mind set of C++ ...
think of your primary program document as your primary CPP file, and anything which is to be program specific is placed within there rather than a seperate .h (thank god pro now allowed for your own include extensions) - however personally to keep things less cluttered within the main loop program mine oftenly consists of a standard template for timer based looping and that is basically as it. apart from the main program functions.
when working on larger projects you come to rely on function as external loops (especially as you can actually place do...loops within them
)
so from this perspective you can consider the functions themselves as objects, within them you can local or global your types, arrays, constants for a very versitile use.
add this is memory pointers for handing data around locally and privately at the same time - this adds a large range of development tools which can then be customised to a more suited environment.
you use the designation CPP for your main source and H for your function include sources (basically the H's are as C++ and the reusable defintions) and you can then start to see how similar you can actually make the development processes
Tsu'va Oni Ni Jyuuko Fiori Sei Tau!
One block follows the suit ... the whole suit of blocks is the path ... what have you found?
