Re: [WDSCI-L] Line truncation message - how to avoid disaster

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Mark

I think you're right about the need for IBM to focus on languages that most 
people use - C/C++ are probably used mostly by business partners developing 
utility and system kinds of things. Phil Coulthard has responded to that 
effect before, and I understand the need to decide where to employ scarce 
resource.

I sometimes use TextPad to edit C code. It, like most Windows editors, has 
no concept of record length. I've got into trouble with this sometimes.

But you can tell it to wrap at a certain number of characters.  But this 
does not put newlines in, however, so it's like most ascii editors, I suppose.

I don't know how CodeWright works - some of us use it here.

SEU has its problems, too - if you overflow a source record, the coursor 
moves to the sequence number field - not a cool thing but we've all got 
used to it.

Wrapping within the record length could be cool.

BTW, I noticed that there is no C/C++ parser under Remote Systems in 
Preferences. I'll look elsewhere, but maybe you know - is it found 
somewhere else - because that is where the preferences for the CL parser 
are actually set.

Regards

Vern

At 10:53 AM 9/20/2003 -0400, you wrote:

> Vern,
>
> I agree it should do this.
>
> Remember though with Code, it had that "/400" in its name.  Even though
> there was a lot of plain editor technology in it, it was clearly made for
> the AS/400.
>
> With JLPEX this has pretty much become true as well, except that when it
> was first created that was not necessarily going to be the case.  The JLPEX
> editor was open sourced with the initial Eclipse 1.0 and was supposed to
> form the foundation of the CDT (C/C++ Development Tooling) that was going
> to be added.  Since C developers for Windows are typically going to use MS
> Visual Studio to write C the market for the CDT was clearly Unix/Linux.
> For whatever reason, the Unix people didn't really like LPEX and decided to
> start over and model their editor after the one that is in Eclipse for
> Java.
>
> To make a long story short, I just do not think that anyone has really done
> anything to the C support in JLPEX since that release.  You have to admit
> that with so much work to do on the RPG/COBOL/CL side of the editor that it
> doesn't make too much sense for IBM Toronto to be doing too much for C at
> this point.  Hopefully either they will get to it or we can figure out a
> way to leverage the Eclipse CDT.
>
> The line length issue is one I had not thought of though.  That obviously
> is not an issue when you are writing C code for Linux/Unix compilers.  So I
> wonder if the editor in the CDT has anything that could even help with
> this?
>
> Mark
>
>
>
>       To:   Websphere Development Studio Client for iSeries
> <wdsci-l@xxxxxxxxxxxx>
>       cc:
>       bcc:
>       Subject:    Re: [WDSCI-L] Line truncation message - how to avoid
> disaster
> Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>
>
> Thanks, Mark, I'll look further.
>
> Yeah, it's my old bugaboo, C.   ;-)
>
> My expectation of JLPEX (promoted by IBM, I believe) is that it'll jave
> "all" the functionality of the LPEX editor of CODE. That one will not allow
> you to go beyond the record length. Now it'd be better, sometimes if it'd
> wrap, IMO. JLPEX knows the record length - as soon as you type or cursor
> past the record length, a left-right scroll bar is displayed.
>
> I think it'd be useful to display the record length somewhere - the
> properties window in the lower left corner does not do so, right-clicking
> to get to Properties does not.
>
> I'd be surprised that an LPEX language profile did not consider the
> iSeries, It seems to me, it did in CODE.
>
> But again, I'll dig a little more.
>
> Thanks
>
> Vern
>
> At 07:21 PM 9/19/2003 -0400, you wrote:
>
> >Vern,
> >
> >What language is this, C?  I think it is parser specific.  The C parser
> >that is there in LPEX was probably originally written without the iSeries
> >in mind.
> >
> >When I am editing CL I do get warning when I go past the end of the line,
> >and if I have the CL formatter turned on, it will automatically fit and
> >wrap the source.
> >
> >Did you go through the LPEX preferences to see if there was anything about
> >line length and wrapping?
> >
> >Mark
> >
> >
> >
> >       To:   websphere Development Studio Client for iSeries
> ><wdsci-l@xxxxxxxxxxxx>
> >       cc:
> >       bcc:
> >       Subject:    [WDSCI-L] Line truncation message - how to avoid
> disaster
> >Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >Sent by: wdsci-l-bounces@xxxxxxxxxxxx
> >Just got the message that says ' Line truncation occurred during the
> save'.
> >I was working in version 5 RSE LPEX, seu editor profile. Unlike CODE,
> there
> >is nothing to stop editing past the record length. I also could find
> >nothing to tell me how long the record is - properties on the source file
> >did not show it in any of the 4 panels.
> >
> >So I need to go back to the green screen or use CODE - after even I am
> >starting to like RSE better!  8-(
> >
> >Please, source files are STILL fixed-length, and that is not going away
> >soon.
> >
> >Regards
> >Vern