×
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.
On 9 March 2016 at 01:07, John Yeung <gallium.arsenide@xxxxxxxxx> wrote:
But if the OP was talking about using CMPPFM as his current workflow,
then surely he is already keeping around multiple "explicit" copies to
compare. It might be more trouble to shoehorn Git into that workflow
than a standalone diff tool, especially since there is a fair amount
to learn about Git if you've never used it before; whereas I think
folks who can figure out CMPPFM can figure out a diff tool pretty
quickly, in most cases without even reading any instructions.
I like your explanation but I'm sure I haven't been clear. OP wants a
better diff than CMPPFM. CMPPFM runs over QSYS.LIB, and pretty much
the only QSYS.LIB alternative to CMPPFM is a full blown IBM i CMS.
Which I very much think a good idea.
I made the assumption that OP isn't interested in that, which means
WinMerge, or one of the *nix diffs like kdiff3. None of those run
over QSYS.LIB source members, so I sort of jumped ahead and answered a
different question: 'How do I get my source members to a diffable file
system?' My personal choice is RDi + Git because t's mostly seamless
to my existing workflow.
-buck
As an Amazon Associate we earn from qualifying purchases.
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.