Program too big to compile

[JAS]

we have a large core program that we are now getting "Program too big to compile" when compiling.
Is this hard restriction or it effected by some settings?

[Geoff Wass [dBVIPS]]

Post by JAS
we have a large core program that we are now getting "Program too big to compile" when compiling.
Is this hard restriction or it effected by some settings?

John,

How big is big? It likely is one line is too big, not the whole program.
Do you use ; a lot to continue lines? If so, check those out.

[JAS]

Geoff
The main wfm is 16K lines+ and results in an .exe of 2.8Mb. Yes there are some long lines - will check them out and see if that solves the problem. Thanks for the sugestion. Is there any finite compile sixe limit? using dBase PLUS 2.6.1.5 b2083
John

Post by Geoff Wass [dBVIPS]

Post by JAS
we have a large core program that we are now getting "Program too big to compile" when compiling.
Is this hard restriction or it effected by some settings?

John,
How big is big? It likely is one line is too big, not the whole program.
Do you use ; a lot to continue lines? If so, check those out.
--
Geoff Wass [dBVIPS]
Montréal, Québec, Canada
.|.|.| dBASE info at http://geocities.com/geoff_wass |.|.|.
.|.|.| ---------------------------------------------------------- |.|.|.
.|.|.| IT Consultant http://Geoff_Wass.com |.|.|.

[Geoff Wass [dBVIPS]]

Post by JAS
Geoff
The main wfm is 16K lines+ and results in an .exe of 2.8Mb. Yes there are some long lines - will check them out and see if that solves the problem. Thanks for the sugestion. Is there any finite compile sixe limit? using dBase

PLUS 2.6.1.5 b2083

Post by JAS
John

John,

Technically, 16,000+ lines in a single .wfm should be OK. However, I
don't recommend it as good programming practice. Do you a lot of
variables in that program?

Have you tried converting a small portion of the program into a comment
and see if that helps. If it doesn't, then likely you have one long line
which you need to find.

[Rainald]

Post by JAS

Post by Geoff Wass [dBVIPS]
How big is big? It likely is one line is too big, not the whole
program. Do you use ; a lot to continue lines? If so, check those
out.

The main wfm is 16K lines+ and results in an .exe of 2.8Mb. Yes
there are some long lines - will check them out and see if that
solves the problem.

As Geoff said, 16.000 lines should not cause a *technical* problem.

But I really wonder *why* you might be working with such a true monster.
And I wonder *how* you might be able to work coding such masses in one
file.

Apart from the technical problem you are facing at present, it is my
urgent recommendation to think about the basic design of your
application and to change the basic construction.

Even in the old procedural days one would not follow an
"all-in-one-sack" principle.
The more in the days of OOP.
Proper design does mean to work with classes and make use of inheritance
by sub-classes. And one would not put all of the classes in just one
file.

Having huge files with tons of lines might have been appropriate in the
days BASIC. It might have been possible in COBOL and FORTRAN.
But in a OOP language one should not work this way.

Just my 2 cents

Rainald

[JAS]

Post by Rainald

Post by JAS

Post by Geoff Wass [dBVIPS]
How big is big? It likely is one line is too big, not the whole
program. Do you use ; a lot to continue lines? If so, check those
out.

The main wfm is 16K lines+ and results in an .exe of 2.8Mb. Yes
there are some long lines - will check them out and see if that
solves the problem.

As Geoff said, 16.000 lines should not cause a *technical* problem.
But I really wonder *why* you might be working with such a true monster.
And I wonder *how* you might be able to work coding such masses in one
file.
Apart from the technical problem you are facing at present, it is my
urgent recommendation to think about the basic design of your
application and to change the basic construction.
Even in the old procedural days one would not follow an
"all-in-one-sack" principle.
The more in the days of OOP.
Proper design does mean to work with classes and make use of inheritance
by sub-classes. And one would not put all of the classes in just one
file.
Having huge files with tons of lines might have been appropriate in the
days BASIC. It might have been possible in COBOL and FORTRAN.
But in a OOP language one should not work this way.
Just my 2 cents
Rainald

Yeh I know that, this is an unusual application in the need to have a lot of info readily available and controlled with some 44 containers for user view. Thanks for comment and we are looking at a different presentation for future releases.