James,
As Matt has pointed out, the text editor solution is perfectly viable,
HOWEVER, I have to side with Jacques on this issue, and suggest that you
break your app into smaller MB files, and use the MapBasic Project (.PRJ)
feature, to pull it all together.
As Jacques suggested, this allows a more "modular" approach to your
software development, and in the long run, should be much more
effective. As an example, when you're debugging a particular segment of
code, you only have to recompile that one segment, instead of the entire
program. You also have the flexibility (as Jacques suggested) of creating
your own REUSABLE "libraries" of code.
I currently have an MBX composed of 5000+ lines and 160+ K of MapBasic
code, and this process works GREAT for me.
HTH.
Dave
At 07:52 AM 11/09/2000, you wrote:
>The file editor option definitely works. Error messages will be saved to
>the same location as the MB is stored, and can be found by selecting 'Error
>Files' from the 'Files of Type' drop-down in MapBasic.
>
>I only found out that there was a size limit when I tried to open and edit
>an existing file in the MapBasic app.
>
>Matt.
>
>-----Original Message-----
>From: Jacques Paris [SMTP:[EMAIL PROTECTED]]
>Sent: 09 November 2000 13:33
>To: James Mazur (EDB); [EMAIL PROTECTED]
>Subject: RE: MI-L MB File Size
>
>64k is not much these days. But MB is what it is with all its
>shortcomings.
>
>The solution of using a text editor is certainly good to overcome this
>limitation. As I have never used it myself, I would not be able to tell
>if the compilation will work when the file is >64k. Fore sure, how will
>the errors be displayed?
>
>I have seen people chopping down the main file by putting sub in
>separate mb files and adding in the main segment some "include
>...xyz.mb". Here again, I am not sure that the 64k could be exceeded at
>compilation time.
>
>My favourite solution is to create semi autonomous segments that can be
>debugged and compiled as mbo. The main segment must have the proper
>"include ..xyz.def" statements and the whole is crowned by a project
>file where the various mbo modules are added to the application. This
>"structure" might appear a little complex at first, but it has the great
>advantage to do all the writing and the compiling under MI, which is for
>guys like me who compose applications by adding and adding... a more
>efficient way to proceed. Note also that some of the mbo can be your own
>library blocks, reusable at will.
>
>But if you can find a MB compiler without the 64k limit, jump on it.
>
>Jacques PARIS
>
>e-mail [EMAIL PROTECTED]
>
>For MapInfo support, see the Paris PC Consult enr. site at
>http://www.total.net/~rparis/gisproducts.htm
>
>For MapBasic questions see the J.Paris site at
>http://www.total.net/~jakesp/index.htm
>
>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]]On Behalf Of James Mazur
>(EDB)
>Sent: November 9, 2000 7:47 AM
>To: [EMAIL PROTECTED]
>Subject: MI-L MB File Size
>
>Hi everyone,
>I am rather new to the MB coding environment and I am a bit confused
>about the issue of the max. MapBasic file size. Is it true that the max.
>file size can only reach 64Kb within the MB editor? My MB script is
>currently at 58Kb and rapidly growing. Should I be using a text editor
>to write the code and then use the "Compile from File" option in MB?
>TIA...your time is greatly appreciated.
>James Mazur
>Mobile Telecom. GIS
>Ericsson, Brasil
>
>
>
>
>
>
> << File: ATT00021.htm >>
>
>
>
>_______________________________________________________________________
>List hosting provided by Directions Magazine | www.directionsmag.com |
>To unsubscribe, send e-mail to [EMAIL PROTECTED] and
>put "unsubscribe MapInfo-L" in the message body.
David L. Dennis
SOFPREP Support Manager Phone: (904) 881-2312
TYBRIN Corporation DSN: 641-2312
[EMAIL PROTECTED] FAX: (904) 881-4985
_______________________________________________________________________
List hosting provided by Directions Magazine | www.directionsmag.com |
To unsubscribe, send e-mail to [EMAIL PROTECTED] and
put "unsubscribe MapInfo-L" in the message body.
