db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David W. Van Couvering" <David.Vancouver...@Sun.COM>
Subject Re: [jira] Commented: (DERBY-516) Need to incorporate client backward/forward compatibility testing into testing procedures.
Date Fri, 14 Oct 2005 15:43:24 GMT
HI, RICK.  I ALSO AM NOT WILLING TO SEND YOU TO THE STAKE FOR THIS ONE. 
  IF I WERE TO USE ANT WITHOUT ANY PRVEVIOUS EXPOSURE I WOULD PROBABLY 
USE CAPS TOO.  SO GO AHEAD AND KEEP IT AS IS!!!!

:)

DAVID

Rick Hillegas wrote:
> Hi David,
> 
> Thanks for vetting my responses. One nub remains:
> 
> I will be happy to change my symbol casing if you feel passionately 
> about this. I think, however, that our existing ant scripts are fairly 
> poor examples of ant usage. For instance, they do not take advantage of 
> the -projecthelp machinery and they jump through crazy hoops because 
> they don't understand custom ant tasks. I think symbol casing is just 
> one example of ant style and usage which needs improvement across our 
> scripts. I, however, am not willing to go to the stake for this heresy 
> and I will defer to your judgment. Please let me know what you think. :)
> 
> Cheers,
> -Rick
> 
> David W. Van Couvering wrote:
> 
>>
>>>
>>> 2) Concerning the casing of my symbols: I have tried to follow the 
>>> same casing policy which I use in Java code. I uppercase constants 
>>> and I camelcase variables, arguments, and methods.
>>
>>
>>
>> I am not sure if the same casing policy applies in Ant, at least I 
>> haven't seen that in the build.xml files we have.
>>
> 

Mime
View raw message