I agree with Bob on this point. IMHO a parameter is 'required' if you must provide a value. In case tapestry will provide a default value, we can keep it optional with a comment, "Default value will only be used if found/contributed ..."
But as far as correct English and developers are concerned, we take all sorts of liberties and expect that from frameworks too. Like Howard said in one of his mails "what the hell is an Environmental anyway?" On Mon, Aug 22, 2011 at 6:17 PM, Thiago H. de Paula Figueiredo <[email protected]> wrote: > On Mon, 22 Aug 2011 07:36:08 -0300, Massimo Lusetti <[email protected]> > wrote: > >> BTW I find completely usual having a piece of software requiring >> something and having another piece of software providing it. >> It seems obvious that the latter could be user's code or another >> module of the same software or a third party module too. > > I don't think this is unusual. It means the component parameter requires a > value, regardless where it comes from. This is not the same as saying the > user is required to provide a value. The requirement here is from the > component parameter view, not the user (developer) one. > > (Breaking the threading because I mistakenly sent the message just to > Massimo instead of to the list and I already deleted the message, so I > cannot reply to it directly). > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Regards Taha Hafeez Siddiqi (tawus) http://tawus.wordpress.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
