I am an exprienced programmer but new to PB/dos. I have a program
written by someone else very poorly. I has 7K lines many statements
per line for about 35K statements. It might be the worst I have ever
seen. It was 18 includes but is now one large file cause PB search
doesn't span files properly. Even though it is supposed to be a
PB3.5 program there were hundreds of reserved word conflicts like
labels called SORT. I have fixed them. I unintelligble errors on
compile. Error 476 shows up at random adding a blank line thousands
of line previous to the error might eliminate it. A DIM xxx(45) turned
in to a DIM xxx(10) midway through the program. That is a reference to
to xxx(33) was okay earlier but then a xxx(11) gives subscript error.
A dim xxx(45) was put in just prior to the error which fixed it. But
the error did not return when that dim was removed. WHAT IS THAT.
I presume that PB does not do a complete syntax check and does not
recover or report internal errors. Maybe if this program was
written from scratch errors would be fixed one at a time. I have
never seen a compiler affected by blank lines (in the right place)
or demonstrate such bizzar behavior.
I have contacted PB support they say there are to many errors
what do I expect the compiler to handle. (I will tell my friends
about that response for years - a compiler that can't handle
and diagnose errors, what's next one that can't handle source?)
What do you do when the compiler explodes. In my 35 years of
programming in languages and assembly I've never seen
anything like it.
JY
written by someone else very poorly. I has 7K lines many statements
per line for about 35K statements. It might be the worst I have ever
seen. It was 18 includes but is now one large file cause PB search
doesn't span files properly. Even though it is supposed to be a
PB3.5 program there were hundreds of reserved word conflicts like
labels called SORT. I have fixed them. I unintelligble errors on
compile. Error 476 shows up at random adding a blank line thousands
of line previous to the error might eliminate it. A DIM xxx(45) turned
in to a DIM xxx(10) midway through the program. That is a reference to
to xxx(33) was okay earlier but then a xxx(11) gives subscript error.
A dim xxx(45) was put in just prior to the error which fixed it. But
the error did not return when that dim was removed. WHAT IS THAT.
I presume that PB does not do a complete syntax check and does not
recover or report internal errors. Maybe if this program was
written from scratch errors would be fixed one at a time. I have
never seen a compiler affected by blank lines (in the right place)
or demonstrate such bizzar behavior.
I have contacted PB support they say there are to many errors
what do I expect the compiler to handle. (I will tell my friends
about that response for years - a compiler that can't handle
and diagnose errors, what's next one that can't handle source?)
What do you do when the compiler explodes. In my 35 years of
programming in languages and assembly I've never seen
anything like it.
JY
Comment