× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Verify vs Compile
  • From: "Vernon Reeve" <reeve@xxxxxxxxxxxx>
  • Date: Mon, 21 May 2001 06:09:17 -0700
  • Importance: Normal

I really don't feel that it defeats the purpose.  If I'm just doing a quick
change, then I don't put it in Code400. But if I'm researching a problem, or
making a lot of changes, then it is much faster to use code400.  Being able
to see over 50 lines of code and being able to split it vertically so I can
see two sets of code on the same display is definitely worth it (I have a
21" monitor).  Not to mention all the other little shortcuts that SEU
doesn't support.   Like to copy a line to the clipboard, I just press
Cntrl-C, to paste it after another line, I press Cntrl-V, to delete a line I
press Cntrl-X, Cntrl Up/Down arrow to select a group of lines, Cntrl M on an
If statement (or whatever) to mark the entire block, Cntrl-K on a field to
show all occurances of it, Cntrl-B shows all the BEGSR lines, and so on.
All these features make it hard to go back to SEU.  (As you can tell, I've
also used the Extras feature extensively to get it set up the way I like
it.)


-----Original Message-----
From: owner-code400-l@midrange.com [mailto:owner-code400-l@midrange.com]On
Behalf Of Phil
Sent: Saturday, May 19, 2001 8:34 AM
To: CODE400-L@midrange.com
Subject: RE: Verify vs Compile

This is what I was doing and I thought it defeats the purpose!

Glad to find out about the cache, and that I have to do a verify prompt
first.  I'm going to try this out.

Phil


-----Original Message-----
From: owner-code400-l@midrange.com [mailto:owner-code400-l@midrange.com]On
Behalf Of Vernon Reeve
Sent: Friday, May 18, 2001 3:25 PM
To: CODE400-L@midrange.com
Subject: RE: Verify vs Compile

I quit using the verify when I started using modules and /copy source to
pull in the prototypes for the modules.  It was taking about 3 hours for it
to do the verify.

Now I have a code400 session going on the PC to modify the source, and I
have another session going on the 400 to compile it.  I then use option 5 to
display the source on the 400 so I can see the compile errors, and use the
PC session to continue to modify it.

It actually works out pretty well.


+---
| This is the CODE/400 Mailing List!
| To submit a new message, send your mail to CODE400-L@midrange.com.
| To subscribe to this list send email to CODE400-L-SUB@midrange.com.
| To unsubscribe from this list send email to CODE400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: larry@paque.net
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.