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



We use Turnover - long in use here. That tool keeps archived versions, and there're ways to compare them - so I'm not sure we need the markers for changes, but we do it pretty extensively. If things get out of hand as described here, we might agree to clean up stuff.

Not completely anal, but getting close - and too close is a bad thing!

Cheers
Vern

On 10/3/2019 11:28 AM, Jon Paris wrote:
I agree - the git approach os much better.

That said there are people anal enough ... I worked with one software vendor who had a tool that compared source code and ensured that no lines were ever deleted or changed without being commented out and the new version (if needed) added in. The result was that after many years it was possible to have to press page down in SEU _18_ times to move from one active source line to the next!!

Mod marks really are an arcane approach.


On Oct 3, 2019, at 12:12 PM, Mark Murphy <jmarkmurphy@xxxxxxxxx> wrote:

Here's the problem with those marks. They are always incomplete unless you
never delete or change a line of code, but always comment out old code and
add replacement code on a new line. I have never met anyone anal enough to
do that 100% of the time. Doesn't mean that person doesn't exist, but just
that I have never met them. With a repository like Git, the computer does
it change tracking, and never misses a change, and never does it in a way
that can't be tracked. The history, in many clients, is color coded so you
know what lines were removed, and which were added, and you code doesn't
end up cluttered with endless comments that are just dead lines of code.

On Wed, Oct 2, 2019 at 8:48 AM Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx> wrote:

Full free pretty much requires a CMS like Git. And in fact, that's my
biggest kick against it. A LOT of people hate mod marks, but I'm not
one of them. I like to be able to bring up source code and be able to
read through the historical changes in a particular routine.

Even with full revision control, it's kind of hard to see the effects of
multiple changes, at least for a novice like me. I think you can get a
list of commits between two dates, and then get the differences for each
of those commits, but I don't know how to get all that information into
a single, comprehensive display.


On 10/2/2019 7:37 AM, Kerwin Crawford via RPG400-L wrote:
I have not written any full free programs YET!
One question. If you use some sort of mod mark system how do you do it?
I have always put comments at the top of the program with the mod mark
and then in positions 1-4 put the mod mark. For example
kc01 // Kerwin Crawford P#2196 kc01
kc01 // The program stopped working when xxx
.
.
.
kc01 // Setll (System:'C ') clients;
kc01 Setll (System:Client) clients;

Note I do not have any sort of CMS.

Kerwin Crawford

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.