Mick,
Yes, you can compile into modules if you wish. But I find that this is
unnecessary. I am unconcerned about file limitations since I use the
GWD text editor.
I have had to reconstruct many .mbo compiled programs that went astray
because of the inability to manage a project that grew and grew with
more and more mbo modules added until it was unmaintainable.
As for code reusability, I am constantly thinking about this when I
write code and have many, many routines put aside that I can just copy
and paste when I need them. Many times I will research a topic by
writing a program to test one specific aspect. After all the querks are
worked out, I integrate it into the main program.
I am sure that mbo and mbp have their use in particular situations but I
have found this to be a problem to maintain.
Carol Sheehan
In message <002501bee6b2$1ef20fe0$c82a8bca@census>, SOLOMON ISLANDS
POPULATION CENSUS <[EMAIL PROTECTED]> writes
>Hello, greetings from the Solomons,
>
>I have been writing a few MapBasic programs for village searches and data
>checking/updating for the village tables we have here. One, which works fine,
>creates a menu, depending on the item selected from the menu another .mbx is run
>to find the input village etc.
>
>I was adapting this for another purpose, but found when I compiled the code it
>created an *.mbo file, not an .mbx file which is what I was expecting. I
>compared the two code listings and the I had not inserted the:
>
>Sub exit_menu
>
> '** Restore default menubar
> Create Menu Bar as Default
>
> '** Exit this application
> Terminate Application "menu.mbx"
>
>End Sub
>
>Having inserted this it works fine.
>The on line help gives me the following:
>
>"If the file compiles successfully, MapBasic creates a filename.MBX file (if the
>file is a stand-alone program) or a filename.MBO file (if the file is part of a
>multiple-module project). If the file generates compilation errors, MapBasic
>displays a list of error messages at the bottom of the edit window"
>
>At the moment, the nature of my relatively simple programs means that I can do
>what I want to do without setting up a multi module project, I do however remain
>slightly confused by the differences between MBX/MBO/MBP and how they all fit
>together etc. and would be interested in any pointers as to when this multi-
>module approach would be worth me exploring further.
>
>Thanks in advance
>
>Mick Saunders
>
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
