× 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.



Dave - I'm posting twice - the built-in is the Eclipse compare, I believe - not useful.

The CODE compare is still with us in some form, just hard to get to from RSE - open a source member, then go to Edit menu and look for the Compare file... item there - badabing!!

HTH
Vern

On 3/13/2012 2:13 PM, Dave Shaw wrote:
I agree - for comparisons the CODE compare is the best, with the Softlanding
extension being a reasonable second place, and the built-in coming in a dismal
third. If all I had available was the built-in, I'd put the source in text
files and use the comparison in Notepad++ rather than use it. I just don't like
it, and I don't understand why IBM couldn't make a better one.

Dave Shaw
Mohawk Industries



----- Original Message ----
From: Jeff Crosby<jlcrosby@xxxxxxxxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio Client for
System i& iSeries<wdsci-l@xxxxxxxxxxxx>
Sent: Tue, March 13, 2012 10:00:51 AM
Subject: Re: [WDSCI-L] Compare showing sequence number differences

IBM had a very functional compare way back in the CODE400 editor. I
still use it and not the LPEX editor compare.

I wasn't aware Softlanding had one . . .


On Tue, Mar 13, 2012 at 9:28 AM,<darren@xxxxxxxxx> wrote:
The RSE extensions do work better. Thank you for the tip. As a short
commentary, I am disappointed that IBM couldn't accomplish something as
basic as a functional compare.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.