How about "local" ? (local to the build file). Jarek ----- Original Message ----- From: "Rodrigo B. de Oliveira" <[EMAIL PROTECTED]> To: "Ian MacLean" <[EMAIL PROTECTED]>; "Jaroslaw Kowalski" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, January 08, 2004 2:06 PM Subject: Re: [nant-dev] custom functions with the script task
> Or, it could default to something like "globals" (globals::my-function()). > > Anyway this expression thing is very good stuff... Thanks. > > Rodrigo > > ----- Original Message ----- > From: "Ian MacLean" <[EMAIL PROTECTED]> > To: "Jaroslaw Kowalski" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Thursday, January 08, 2004 6:09 AM > Subject: Re: [nant-dev] custom functions with the script task > > > > Oh really ? ok in that case the namespace attribute will be required. > > Ian > > Jaroslaw Kowalski wrote: > > > > >>I think add the namespace attribute but make it non-required. Just the > > >>global namespace if its present. Since none of the built-in functions > > >>reside in the global namespace that shouldn't be a problem. > > >> > > >> > > > > > >I'm afraid there's no global namespace ;-( And parser does rely on the > fact > > >that every function is prefix::function-name()... > > > > > >Jarek > > > > > > > > > ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
