From: Ian MacLean [EMAIL PROTECTED]
Sent: Friday, September 10, 2004 1:12 AM
If this is still true then I wonder how the parallel task in Ant works
around it.
Properties in Ant are always read-only, so there shouldn't be any issue
unless two parallel tasks attempt to create the same new
I'm in the process of implementing a parallel type task (similiar to the
existing Ant task).
I've pretty much got it working and was playing with it in our current build
file. The first thing I found was that properties that are declared within
a target are global in scope. Needless to say,
Andy Sipe wrote:
I'm in the process of implementing a parallel type task (similiar to
the existing Ant task).
I've pretty much got it working and was playing with it in our current
build file. The first thing I found was that properties that are
declared within a target are global in scope.
Denny; Scott Hernandez; [EMAIL PROTECTED]
Subject: Re: [nant-dev] Property Scoping
To be honest I'd like to see us release a 1.0 with the current feature
set before implementing somthing like typed properties.
it would be kinda nice to unify properties and type references which are
both essentially
To be honest I'd like to see us release a 1.0 with the current feature
set before implementing somthing like typed properties.
Agree. Still I'd like to see some verbosity patch and fileset extensions in
1.0 somehow. Hope those will find its way into 1.0 even they are not in
release plan.
it
Yeah, I was considering the same thing. I also wondered whether this
could mean that there could be a unified type system. Filesets, string
properties etc.
You mean storing a fileset inside a property? Interesting idea.
Oh - we already mention it before. Would be great! And also +
Oh - we already mention it before. Would be great! And also + operator in
expressions could be overriden to fileset merge :) And functions with
fileset argument could exists instead of string as refid to fileset etc
etc
etc...
The overload is a bad idea. Currently it has problems with strings
To be honest I'd like to see us release a 1.0 with the current feature
set before implementing somthing like typed properties.
it would be kinda nice to unify properties and type references which are
both essentially different types of variables. However I do feel that
this is peripheral to
Sure this is clean in a mathematical sense but personally I'd rather see
a more verbose layout that actually gives me an idea of what files the
fileset will match just by looking at it. Given that it can be hard to
determine what a given fileset will match right now I imagine it will be
that
- Original Message -
From: Ian MacLean [EMAIL PROTECTED]
To: Jaroslaw Kowalski [EMAIL PROTECTED]
Cc: Mitch Denny [EMAIL PROTECTED]; Scott Hernandez
[EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Thursday, January 22, 2004 9:07 PM
Subject: Re: [nant-dev] Property Scoping
To be honest I'd
Seems like the flow scope should be called local in C#/programming
terms, and local would be private/container-only scoping. Having global be
the default is a good call, but only in come case, as you have identified in
if//foreach//etc.
I'm sure we will be able to say more with a patch; so we can
) 610141
-
-Original Message-
From: Jaroslaw Kowalski [mailto:[EMAIL PROTECTED]
Sent: Thursday, 22 January 2004 6:37 AM
To: Mitch Denny; [EMAIL PROTECTED]
Subject: Re: [nant-dev] Property Scoping
Hi Mitch!
property name=x value=y accessibility=Global /
Global is actually the default. If I
.
- Mitch Denny
- [EMAIL PROTECTED]
- http://www.monash.net
- +61 (414) 610141
-
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott
Hernandez
Sent: Thursday, 22 January 2004 7:37 AM
To: [EMAIL PROTECTED]
Subject: Re: [nant-dev] Property
-
-Original Message-
From: Jaroslaw Kowalski [mailto:[EMAIL PROTECTED]
Sent: Thursday, 22 January 2004 7:50 AM
To: Mitch Denny; Scott Hernandez; [EMAIL PROTECTED]
Subject: Re: [nant-dev] Property Scoping
Scott,
I'd really prefer to branch on this - it has the ability to really
break things. One
14 matches
Mail list logo
