Brendan's Posting

> Well this didnt work, so I tweaked everything (the compiler doesnt tell
> you
> why the program wont compile), and ended up with one change that is now
> obvious, the ENTRY should be:
> ENTRY * (*ENTRY) EXT;
> 
> I've run it and it works.
> 
> I think that this technique has potential... but a little help is needed.
> I
> shall try something more ambitious, but I shall get in trouble when the
> compiler fails - is there a way of determining which line is causing a
> problem?
        [Leif Svalgaard]  Most of the time the compiler will tell you
        at the bottom of the listing (wrksplf to see them). Unfortunately
        for you, when the errors have to do with parameter lists or
        operand lists, you don't get any info. but, the fact that you
        don't get anything simply means that you should check
        parameters and operand lists.

        I have a program that runs a PC and checks the syntax of
        an MI-program with much better and nicer error detection
        that the AS/400 compiler. I could send you that if you
        want. There is one problem with it, namely that it is rather
        old and MI has evolved a bit, so some of the newer stuff
        are flagged as errors. One day when I have time (???)
        I'll fix that...
>  
+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---