Hi Terry,

I'm in agreement. I like the autoformatting in CL, and do not like how it moves a comment from before the command to after the command. I don't use those types of comments a lot, but when I do, I want the first thing read is the comment at the beginning. When the comment comes after, it doesn't seem right to me.

Kurt Anderson
Sr. Programmer/Analyst - Application Development, Service Delivery Platform

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Terry Hertel
Sent: Thursday, May 01, 2014 12:44 PM
To: 'wdsci-l@xxxxxxxxxxxx'
Subject: [WDSCI-L] Auto-formatting of comments in CL

For the most part I like the way the editor indents and formats CL. What I don't like is that it moves my comments (change notations) from the front of the command to the end, so added lines don't stand out as well, especially if the command spans multiple lines. And no, I do not display or the date column because it makes it hard to find all of the changes made for a specific request/project. I was thinking about submitting an RFE asking for an option that would allow comments entered in the space before the indent value to be frozen and not moved, but don't want to bother if others wouldn't be affected or support the request. What do others think?
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.