×
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 2012/5/18 4:42 PM, rick baird wrote:
We've changed the way we mark our code changes which required updating
comment lines in the source members to initialize them for the new
method.
Why not wait until the source member needs to be changed for some other
reason?
I'm assuming there's a good reason, I'm just curious to know what it is.
The only thing I can think of is that there's some utility that crawls
through the source analyzing changes - if not, ignore the rest of this.
If so, shouldn't the utility just handle both the old and new format? If
it can't, then some pre-process could do whatever transformation is
being done on the source now, but into temporary members.
I agree with Chuck - faking out the last change date on the file could
have unforeseen consequences, and if you are unlucky, you wouldn't find
out about them until long after the badness happened.
Rule to live by: There's always another way.
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.
midrange.com
