Hey Ryan, Check the docs of the <sysinfo> task. Note that its not officially deprecated, so I'd still fix any issues.
Gert -----Original Message----- From: Ryan Boggs [mailto:rmbo...@gmail.com] Sent: vrijdag 26 maart 2010 15:53 To: Dominik Guder Cc: nant-developers@lists.sourceforge.net Subject: Re: [nant-dev] sysinfo task Hi, On Mar 26, 2010, at 2:07 AM, Dominik Guder <o...@guder.org> wrote: > Am 25.03.2010 17:12, schrieb Gert Driesen: >> Hi Ryan, >> >> I guess it won't make it in time for the 0.90 release. >> Personally, I even consider the sysinfo task deprecated. >> >>>>> >>>>> On Mar 25, 2010, at 8:10 AM, "Gert Driesen" <gert.drie...@telenet.be >>>>> > >>>>> wrote: >>>>> >>>>>> Ryan, >>>>>> >>>>>> We cannot allow parenthesis in property names, as that would >>>>>> screw >>>>>> up our expression tokenizer. >>>>>> I'm more enclined to a machanism that allows explicit control >>>>>> over >>>>>> the property names that a given environment variable is mapped >>>>>> to. >>>>>> Something similar to the file mappers in Ant would be great. >>>>>> >>>>> If I understand you correctly, are you referring to something >>>>> like: >>>>> >>>>> <sysinfo> >>>>> <mapper type="glob" from="*(* to="*_*" /> >>>>> </sysinfo> >>>>> >>>>> Am I understanding you right? >>>> > > Hi, > > sorry, I did not write that I checked the parens handling in > properties and found out that the parser will fail. The mapper > solution > looks good but as Gert stated <sysinfo> is kind of deprecated. So we > might not put to much effort into it. Does anyone know if <sysinfo> was replaced by anything? This would be good to know. > Another point which needs attantion (propably for 1.0) is that I was > able to define a property with parens without getting an exception at > definition time. More detail later. > Can you provide an example when you get a moment? I would like to look into this. > First of all I want to get these tests green for 0.90 release. > My proposal: > - add "failonerror='true'" to all existing tests > - add a new test which throws BuildException for > "Environment.ProgramFiles(64)" > - fix docu > - sort output > > What do you think? > I like it. > Regards Dominik > > -- > The answer to the great question of life, > the universe and everything is 42 (Douglas Adams) > > --- > --- > --- > --------------------------------------------------------------------- > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > nant-developers mailing list > nant-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nant-developers Thanks, Ryan ---------------------------------------------------------------------------- -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.733 / Virus Database: 271.1.1/2769 - Release Date: 03/25/10 21:50:00 ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
