Syntax checking as you type

[Guest.Visitor]

I've just finished my first program with CODE/400 and have one major gripe. The syntax checker tells me when I have a problem, but then I not only have to delete the error line, but move back up and fix the problem. SEU quickly positions the cursor where the error is and lets me fix it instantly. In fact, I rely on it to position the cursor for me, usally leaving required fields other than opcode blank. Having to tab back and forth, and then the extra time to delete an error message and move back up, significantly impacts my time. Perhaps it is just a matter of getting used too, but I regard this is a serious drawback of CODE. Or could there be a setting to make it behave exactly like SEU in this regard? I looked but can not find anything. Thanks, Richard Evans

[Guest.Visitor]

Hi Richard. After a year, I still find things with Code/400 that I dislike and new things that make it worthwhile. You do not have to delete the error line(s). The next time you do the Verify, the error line(s) will be removed from the source, if fixed. My latest gripe is the INSERT disability when using the /free environment. I now CTRL/END the CTRL/X to copy/delete from x to the end of the line and then type my addition and the hit CTRL/V to add the code I just deleted. This just to insert a character or two. -Mean 1

[JonFParis]

Wouldn't it be a lot easier to position the cursor and type Alt + S (split) - this is what I use all the time and have done for years. If a coding change enables a line to fit when it didn't before Alt + J (Join) will do the job. If you are unfamiliar with these keys check out Help > Keys Help for a full list. "Mean 1" <Mean_1@mcpressonline.com> wrote in message news:6ae3daa7.0@WebX.WawyahGHajS... > My latest gripe is the INSERT disability when using the /free environment. I now CTRL/END the CTRL/X to copy/delete from x to the end of the line and then type my addition and the hit CTRL/V to add the code I just deleted. This just to insert a character or two. > > -Mean 1

[JonFParis]

I've never heard this complain before. Unlike SEU, Code syntax checks the line the minute you leave it. Since you imply that SEU does it "instantly" I can only assume that you only ever use SEU in prompted mode. I hardly ever used prompt in SEU so the fact that Code shows me errors as I move off the line is a blessing for me. It used to drive me nuts in SEU that I would make a bunch of changes on the screen and only when I pressed enter (or paged) did I know I had an error. If you use Code prompted it will behave more like SEU. You certainly _don't_ have to delete the error lines - they go away the instant you correct the error. In fact it is only when the editor gets _really_ confused that you ever have to delete error lines. Even the verifier/compiler feedback error lines go away by them selves when you next verify/compile. Did you go through IBM's introduction to the editor or use our QuickStart guide (www.Partner400.com) ? They would have demonstrated these kind of features to you before you began. "neppie" <neppie@nospam.net> wrote in message news:Xns92926BAF158A5neppienospamnet@207.25.253.14 ... > > I've just finished my first program with CODE/400 and have one major gripe. > The syntax checker tells me when I have a problem, but then I not only > have to delete the error line, but move back up and fix the problem.

[Guest.Visitor]

I doth quote yon "Jon Paris" <Jon.Paris@Partner400.com> in saying: > I've never heard this complain before. Unlike SEU, Code syntax checks > the line the minute you leave it. Since you imply that SEU does it > "instantly" I can only assume that you only ever use SEU in prompted > mode. I hardly ever used prompt in SEU so the fact that Code shows me > errors as I move off the line is a blessing for me. It used to drive > me nuts in SEU that I would make a bunch of changes on the screen and > only when I pressed enter (or paged) did I know I had an error. If > you use Code prompted it will behave more like SEU. > > You certainly _don't_ have to delete the error lines - they go away > the instant you correct the error. In fact it is only when the editor > gets _really_ confused that you ever have to delete error lines. Even > the verifier/compiler feedback error lines go away by them selves when > you next verify/compile. > > Did you go through IBM's introduction to the editor or use our > QuickStart guide (www.Partner400.com) ? They would have demonstrated > these kind of features to you before you began. > > "neppie" <neppie@nospam.net> wrote in message > news:Xns92926BAF158A5neppienospamnet@207.25.253.14 ... >> >> I've just finished my first program with CODE/400 and have one major > gripe. >> The syntax checker tells me when I have a problem, but then I not >> only have to delete the error line, but move back up and fix the >> problem. > > > Jon - The way *I* understood the original post reminded me of the way one of the programmers here works. He'll key an 'I' to insert a line, key a 'C' to identify the line as a Calc-spec, then hit Enter. He does this for as many lines as he thinks he's going to need (only saw this when he was adding a limited number of lines) and on the last one, just hits Enter to end entering new lines. SEU places his cursor back at the first 'C' spec in the Opcode column. He keys his opcode and presses Enter. The SEU syntax checker then throws his cursor into the 1st column where data's required for that opcode he entered (i.e., "CHAIN" moves his cursor to Factor 1, "CLEAR" moves it to Factor 2, etc.). Once he's entered all the required fields to satisfy the opcode entered, his cursor's moved to the next line, ready for the next opcode. He's done it for so long, he's gotten pretty fast at keying data in. My take on the original post was that "neppie" wants his cursor to jump to the field in question - for example, Factor2 if he simply keyed "Clear" and hit Enter. The error message would display once he keyed an entry in the missing field, I don't think he realizes that, though. By the way, I read your quickstart guide. I helped with IBM's intro, but still managed to learn from your (and Susan's?) write-up. Thanks to both of you! -- David Schopp WISDM Team Leader Computers Unlimited

[Guest.Visitor]

Exactly. I certainly DO NOT use prompting! By letting SEU position the cursor I only type relevant code and don't waste time navigating on the screen. It may sound negligable but in the course of writing a program from scratch it can be a significant time saver. The "CLEAR" opcode was a perfect example: When designing my first program with CODE/400 I repeatedly put the record name to be cleared in Factor 1. I've been programming long enough to know better, but with SEU I never had to even stop and think about it. I just typed where it put the cursor. > > Jon - > > The way *I* understood the original post reminded me of the way one of > the programmers here works. He'll key an 'I' to insert a line, key a > 'C' to identify the line as a Calc-spec, then hit Enter. He does this > for as many lines as he thinks he's going to need (only saw this when > he was adding a limited number of lines) and on the last one, just > hits Enter to end entering new lines. > > SEU places his cursor back at the first 'C' spec in the Opcode column. > He keys his opcode and presses Enter. The SEU syntax checker then > throws his cursor into the 1st column where data's required for that > opcode he entered (i.e., "CHAIN" moves his cursor to Factor 1, "CLEAR" > moves it to Factor 2, etc.). > > Once he's entered all the required fields to satisfy the opcode > entered, his cursor's moved to the next line, ready for the next > opcode. He's done it for so long, he's gotten pretty fast at keying > data in. > > My take on the original post was that "neppie" wants his cursor to > jump to the field in question - for example, Factor2 if he simply > keyed "Clear" and hit Enter. The error message would display once he > keyed an entry in the missing field, I don't think he realizes that, > though. > > By the way, I read your quickstart guide. I helped with IBM's intro, > but still managed to learn from your (and Susan's?) write-up. Thanks > to both of you! >

[Guest.Visitor]

I doth quote yon neppie <neppie@nospam.net> in saying: > > > Exactly. I certainly DO NOT use prompting! By letting SEU position > the cursor I only type relevant code and don't waste time navigating > on the screen. It may sound negligable but in the course of writing > a program from scratch it can be a significant time saver. > > The "CLEAR" opcode was a perfect example: When designing my first > program with CODE/400 I repeatedly put the record name to be cleared > in Factor 1. I've been programming long enough to know better, but > with SEU I never had to even stop and think about it. I just typed > where it put the cursor. > <snip> >> My take on the original post was that "neppie" wants his cursor to >> jump to the field in question - for example, Factor2 if he simply >> keyed "Clear" and hit Enter. The error message would display once he >> keyed an entry in the missing field, I don't think he realizes that, >> though. >> Well, neppie, since this is the case, Codeedit doesn't function that way. It tells you if you've made a mistake, but doesn't move your cursor around for you. -- David Schopp WISDM Team Leader Computers Unlimited

[Guest.Visitor]

The strict syntax rules of RPG make it ideal for that type of "smart" editing. It is a shame it was not incorporated into an editor used primarily for RPG. Hopefully IBM will consider adding that functionality. If they really want to get people (at least me) to move away from the green screens they'll have to. Currently that drawback, combined with the communication delays, equate to too much lost productivity. I will continue to use the screen designer, I think. I've yet to have a project that requires subfiles since I started experimenting with them but it looks like that piece WILL save time over SDA. > Well, neppie, since this is the case, Codeedit doesn't function that > way. It tells you if you've made a mistake, but doesn't move your > cursor around for you. > >

[JonFParis]

> Exactly. I certainly DO NOT use prompting! By letting SEU position the > cursor I only type relevant code and don't waste time navigating on the > screen. It may sound negligable but in the course of writing a program > from scratch it can be a significant time saver. So you basically keep hitting Enter and wait for the 400 to get back to you? It is interesting though that you're exploiting a "feature" that was never intended to be such. There must be times when it doesn't work properly either I suspect but .... I still would not give up verify etc. for that. If it was that important to me, which it isn't, I'd look for a way to program it so that the tab key (or something) moved the cursor to the next required entry rather than give up everything else for one feature. Just my perspective - I've bee using Code for so long now that the agony of having to de _anything_ in SEU is almost unbearable.

[ngg@aim-software.co.uk]

It always works, and if you're coding at speed, it's a massive timesaver. This is to me a huge drawback in Code Editor. I will continue to use SEU as it is much quicker to use. "Jon Paris" <Jon.Paris@Partner400.com> wrote in message news:ana2dd$40kk$2@news.boulder.ibm.com... > > > Exactly. I certainly DO NOT use prompting! By letting SEU position the > > cursor I only type relevant code and don't waste time navigating on the > > screen. It may sound negligable but in the course of writing a program > > from scratch it can be a significant time saver. > > So you basically keep hitting Enter and wait for the 400 to get back to you? > It is interesting though that you're exploiting a "feature" that was never > intended to be such. There must be times when it doesn't work properly > either I suspect but .... > > I still would not give up verify etc. for that. If it was that important to > me, which it isn't, I'd look for a way to program it so that the tab key (or > something) moved the cursor to the next required entry rather than give up > everything else for one feature. > > Just my perspective - I've bee using Code for so long now that the agony of > having to de _anything_ in SEU is almost unbearable. > >