I think using the common known style is better. But you can implement as you want :-)
Jan > -----Original Message----- > From: Jose Alberto Fernandez [mailto:[EMAIL PROTECTED] > Sent: Monday, September 08, 2003 12:53 PM > To: Ant Developers List > Subject: RE: [SUBMIT] optional task <propertyformatter> > > > Could we move away for the "C" cryptic naming conventions, please? > The main user community here comes from Java, I think. I do not think > we need regress to "C" (8 chars limitation on names). > > :-) > > Jose Alberto > > > -----Original Message----- > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > > Sent: 08 September 2003 06:17 > > To: [EMAIL PROTECTED] > > Subject: RE: [SUBMIT] optional task <propertyformatter> > > > > > > > > First thought on that topic is a kind of printf > > > > <printf property="" refids="" format=""/> > > > > where > > > > property takes the name of the new created property > > > > refids takes a list of (:,;) separated names of > > properties > > > > format takes the format string like in printf > > > > > > > > That would be much more powerful than these predefined formats. > > > > > > > > > > I like that idea, but still think offering a simpler task > > > that has some > > > predefined formats is a good thing. I can't count the times I > > > got a sprintf > > > format wrong, or had to sit there and play a while till I got > > > what I wanted. > > > Even after reading the docs for sprintf. > > > > > > -- Larry > > > > > > Ok, an additional attribute <sprint ... preformat=""/> could > > do that. Advantage would be to have the same task. > > > > > > Jan > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
