|
There is STILL a long standing bug in the "indenter"; two years ago it worked great. OR maybe it is fixed now? Here is a great way to use the indent function: 1) Open a member for edit. 2) Remove the line numbers from view. 3) Split the screen, VERTICALLY. If you use the GUI and split the screen vertically, you can see more code. No RPGer wants to split the screen horizontally! 4) Indent the new window on the right. It was great! Edit on the left, view indented code on the right window. My current problem is when I indent the second window (#4 above). Now I get three horizontal windows. Less lines of code then SEU! Please help; I would like the old functionality back. Don. -----Original Message----- From: Booth Martin [mailto:Booth@MartinVT.com] Sent: Tuesday, April 30, 2002 2:47 PM To: code400-l@midrange.com Subject: Re: Line number for missing ENDyy? -- -- [ Picked text/plain from multipart/alternative ] Wasn't there an Item "Indent" under the "View" on the Code/400 menubar? This item will open your source in a view where you can follow all of your EndYYs and see where its gone amiss. The line that shows the error is not always the line where the real error is, in the logic flow. Also under "View" is "Split" and you can have the views shown one above the other like we're used to with F15, or side by side which is nicer when we get out of the 80/132 column world. --------------------------------------------------------- Booth Martin http://www.MartinVT.com Booth@MartinVT.com --------------------------------------------------------- -------Original Message------- From: code400-l@midrange.com Date: Tuesday, April 30, 2002 14:35:19 To: code400-l@midrange.com Subject: Re: Line number for missing ENDyy? Booth, I looked under "View" in the error list and "View" in CODE/400 Editor under everything that I could find that might apply to my problem. I do not see anything that would link the statement number to a line or sequence number. I still have to look at the compilation to get the sequence number. I looked under many other menu options trying to find one that might apply. Could you be more specific? Thanks, Craig Strong ** Booth wrote: Look under "view --------------------------------------------------------- Booth Martin http://www.MartinVT.com Booth@MartinVT.com --------------------------------------------------------- -------Original Message------- From: code400-l@midrange.com Date: Tuesday, April 30, 2002 11:38:27 To: code400-l@midrange.com Subject: Line number for missing ENDyy? Can we get to the line number of the error about missing ENDyy in CODE/400 without looking at the compile listing? If so, can the link (line number) be included in the corresponding member of the event file EVFEVENT on the AS/400 or C:\WDT400\Tmp\XXXX.EVT like other errors? That way we can get to it by a double-click on the error in the error list. Since I have been trying to use the Verify Program function more, I have noticed this more. I had some good IF statements in my RPG and I forgot an ENDIF. Using either compile or verify, I got "RNF5177 ENDyy operation missing for ELSE operation group at statement 1662; END assumed." In the error list, double-clicking on this error went to the beginning of the source and showed the error in pink there. The best way I knew to find this error in the source, was to look at the compilation, find statement 1662, find the sequence number to the very right, then locate the sequence in CODE/400. Obviously, this process does not work on a verify if there is not a current compile listing. I thought sequence numbers were saved in the event file, but when I looked at the file, it turns out that line numbers are being saved, except for missing ENDyy errors. I don't see line numbers anywhere in the compile listing, so they must be a calculation or stored somewhere else. Would it be possible to scan the RNF5177 error line for "statement X" where X is the statement number of the error, find it in the compilation, calculate the line number based on the sequence number at the very right, and store it in the event file? This has probably already been considered and there is also probably something I am not aware of. I thought I should bring it to the attention of someone in case they weren't aware. I haven't found a discussion of this topic on this list. Thanks, Craig Strong _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l or email: CODE400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-l. . -- [ Content of type image/gif deleted ] -- _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l or email: CODE400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
