|
I guess I would allow different naming conventions to be selected (camel hump, etc) or you could go to an advanced tab and type in what you would like each one to be (I am talking bifs now). >For example, you use "SubSt", although "substring" is really a single word. D'oh! In my mind I always view it as two words, don't know why. <Aaron goes to change %SubSt to %Subst in all of his code> Buck, the macro is a good idea, can you automatically execute a macro when you save your code? It would be nice if I didn't have to do additional steps (yes I am lazy:-). Aaron Bartell -----Original Message----- From: Joe Pluta [mailto:joepluta@xxxxxxxxxxxxxxxxx] Sent: Wednesday, May 21, 2003 11:31 AM To: Websphere Development Studio Client for iSeries Subject: RE: [WDSCI-L] Auto correct syntax for opcodes and bifs > From: Bartell, Aaron L. (TC) > > We have a new standard in our shop to have the first letter of all > opcodes and bifs be capitol and each word there after in the name. (snip) > Could it be added as a feature to allow you to specify what naming > convention to use when viewing source? My only concern is that what constitutes a word might be a little different from one company to another. For example, you use "SubSt", although "substring" is really a single word. So how do you handle these sorts of situations? Do you have a panel that shows every possible keyword and then the "preferred" capitalization? I don't know the answer. Joe _______________________________________________ This is the Websphere Development Studio Client for 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 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.