RE: *CURRENT library? was RE: (no subject)

["Phil" <sublime78ska@xxxxxxxxx>]

Phil,

I recently had the need to edit C source in a *STMF.  In CODE (WDTS 5.1),
the support to browse, open, and save to an IFS file is ungainly.  Is this
better in the new lpex editor?  Does the editor allow you to select which OS
version to edit for?  Does the compile options allow for selecting which
release the OS is on? (not just tgtrls, but the actual command. This is
really important for C because the CRTCMOD command between V4R5 and V5R1 is
very different.)

Phil G.

->-----Original Message-----
->From: code400-l-admin@midrange.com
->[mailto:code400-l-admin@midrange.com]On Behalf Of coulthar@ca.ibm.com
->Sent: Sunday, October 13, 2002 11:47 AM
->To: CODE400-L@midrange.com
->Subject: RE: *CURRENT library? was RE: (no subject)
->
->
->Regarding CL prompting in the CODE editor, yes it does require interactive
->STRCODE today,
->although there is a patch on the Web site I believe that will allow it to
->work with autostart servers
->by using the AS/400 Toolbox for Java to do the F1 and F4 support.
->
->In the new RSE editor we do not require an autostart server for
->CL editing,
->as we use that toolbox support.
->
->Within the new RSE, you have the choice of launching the new
->iSeries Editor
->or the classic CODE
->Editor. The new one is based on lpex ... but it is a new Java version of
->LPEX, not the original C++-based
->version. On top of that core editor comes all the OS/400 and
->language-specific functionality, and that
->is what we are working to continue porting to Java. It is our goal,
->ultimately, to not only match the CODE
->editor but indeed to surpass it in some way. Eg, imagine typing a '%'
->character and seeing a popup
->list of built-in functions to select from. Same goes for the RSE
->non-editing functionality ... it will surpass
->both PDM and CPO. We know this is a base requirement, and we trust you to
->hold us to it!
->
->Phil Coulthard, iSeries Software Architect,  IBM Canada Ltd.
->coulthar@ca.ibm.com. 905-413-4076, t/l 969-4076
->
->----- Forwarded by Phil Coulthard/Toronto/IBM on 10/13/2002 11:33 AM -----
->
->                      Vernon Hamberg
->                      <vhamberg@attbi.c        To:
->code400-l@midrange.com
->                      om>                      cc:
->                      Sent by:                 Subject:  RE:
->*CURRENT library? was RE: (no subject)
->                      code400-l-admin@m
->                      idrange.com
->
->
->                      10/13/2002 08:19
->                      AM
->                      Please respond to
->                      code400-l
->
->
->
->
->
->Thanks, Phil
->
->What do they say? Don't ask why? As you know, *CURLIB is
->troublesome. E.g.,
->our build programs will sometimes change it. I'll need to check that it's
->still OK to do this while using CODE. For now, I assume it's alright to
->change it in the session, once it's started.
->
->Re: changes - CL prompting right now requires a STRCODE session - doesn't
->work with autostart server. Is this right? Does prompting work without
->STRCODE in the RSE connection?
->
->As I know you've heard, and I'm sure you are aiming for, RSE has to have
->the full functionality of CODE. You already have LPEX in RSE, and CODE is
->based on LPEX, right?
->
->_______________________________________________
->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.
->
->NOTE: WDSc for iSeries disucssion has it's own mailing list.
->Information can be found at
http://lists.midrange.com/cgi-bin/listinfo/wdsc-l