Who understands the compiler?


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]

Posted by Stephen Auerbach on March 11, 2005 at 07:26:56:

1)Conditional Compile Commands make it possible to include or exclude sections of code in a program. However, when you compile and list a program with a block of code excluded you will be very surprised to see that the excluded lines of code print on the listing. There is no way to get a source listing that matches the compiled code. You can not verify that your .IF statements did what you wanted.

2) Warning. Unreferenced variables. The compiler insists on reporting unreferenced variables. Unfortunately it tells you about variables in USEFILES that are defined but never referenced. Of course, there is nothing you can do about them; they are in the USEFILE for some reason and can not be deleted; so you train your brain to ignore warning messages and finally, one day, you think, “Why does this thing nag me all the time?”

3)On the other hand, the compiler does NOT report unreferenced statement labels. That might prove useful - eliminating unneeded code can help you understand a program better; knowing that the apparent secondary entry point into a routine is never used is meaningful.

How about a Release 2.0 of the Internet Basic Compiler?



Follow Ups:



Post a Followup

Name:
E-Mail:

Subject:

What is the name of the main Signature System's Product?

Comments:

Optional Link URL:
Link Title:
Optional Image URL:

You may attach up to 5 files to your followup (see below):






[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]