Program Structure

Since I come from a C programming background I tend to structure my programs. Ebasic itself does not enforce programming structure so you can write in a method which feels most confortable for you.

The structure I like to use is:
A Header - provides some information about the Program. Include Files - these are for declarations used in more than one module including Globals. Constants and Definitions - local items used in this module. The main process - this is the area that is the starting point for the code. Subroutines - The actions taken on events. The Main Window Subroutine - defines the main window for this program. The Primary Handler - The core event handler. The Main Process Subroutine - The process holder. The Close Process - Cleanup and exit The 'on-click' Subroutines - how to handle click events.

The only Ebasic requirement is that any required subroutine declarations, constants, and variables(under certain conditions) be declared before they are used.

The structure you choose will most likely be different than mine but feel free to follow mine if you like.

The important thing is that you form your personal structure and be consistent in the way you build your programs.

You should decide on what structure you will be using, refine it, and stick to it.

Next Section