I definitely think that defining what a legal property name is would be a big benefit.
As it stands, "" is a legal property name, I can write and it's legal. This has a practical
consequence, in that I think it's currently impossible to correctly parse the -D
argument if you don't know what th
Gerry wrote:
>
>
>
>
>
>
>
I have to admit, this is a nice simple way to handle conditional execution
of tasks. How about just limiting the expression evaluation to the
if/unless attributes, and only permitting expressions similar to those in
the C# preprocessor (!, ==, !=
Bill wrote:
> Unwieldy in my mind means I *have* to do a lot of complicated things
> in order use the tool effectively. The mere existence of complex
> functionality simply means the tool is powerful.
I was meaning unwieldy from a maintenance point of view. For example,
Programmer A writes a bun
Mark:
>If the extra (complex) functionality is there then it will be used,
>and NAnt will get a reputation for being unwieldy.
Unwieldy in my mind means I *have* to do a lot of complicated things in
order use the tool effectively. The mere existence of complex functionality
simply means the tool
Gerry Shaw:
>I do understand the slipperly slope of this but what I'm trying to do is
>make writing complicated tasks feasible.
In my mind the good design of a powerful tool makes it easy to do common
things, and possible to do things however the user wants -- including
things the designer may n
The main function I wanted was something to evaluate expressions so I could
write tasks like this:
I figured this was a two step process:
1. Getting a function that could evaluate expressions
2. Changing how if/unless work so that the string passed in gets passed to
the Ev
nal Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Ian
> MacLean
> Sent: 28 August 2002 01:50
> To: Shaw, Gerry
> Cc: [EMAIL PROTECTED]
> Subject: Re: [nant-dev] Property names and functions
>
>
>
> >
> >I'm starting wor
>
>I'm starting work on adding functions to nant and the syntax I was
>thinking of using is this:
>
>
>
Are we sure we need this. No disrespect but couldn't we do a lot of
whats in these functions using the script task ?. Its a slipperly slope
to be taking - just look at how xslt has evolved
What do people think of restricting property names to the following
regular expression:
^([\w-\.]+)$
This would mean that only:
A-Z a-z 0-9 and '-' '.' would be allowed. If someone wants to restrict
it further to prevent leading numerics and - or . characters that would
be fine.
I'm starting
