Comments for Neo Fight!

Comment on Microsoft Parallel Extensions – Hard”core” code made easy! by Shaun McCarthy

Shaun McCarthy — Fri, 08 May 2009 18:27:25 +0000

Thanks Phil – yeah, the Parallel Extension library is “CTP” rather than fully tested, so I wouldn’t use it to run a bank’s processing system

Bring on .net 4.0!

Comment on Microsoft Parallel Extensions – Hard”core” code made easy! by Phil Scott

Phil Scott — Fri, 08 May 2009 17:49:07 +0000

I briefly used that library, but I was finding that it would randomly leave the cpu hanging at 100%. It didn’t seem to be cleaning up right. I tried explicitly disposing of the TaskManagerPolicy, but that was not only a pain in the ass but also not very consistent.

Just wanted to give a heads up to people that this code isn’t production ready. I still use it in throw away apps that I run locally, but for code that we are shipping I’m using the ThreadPool by hand.

Comment on Parsing Command Line Arguments by Dugmulkelunny

Dugmulkelunny — Tue, 17 Feb 2009 13:58:09 +0000

neofight.wordpress.com – cooooolest domain name)))
————————
internet signature: http://potet.ru/

Comment on Alpha released by Tim

Tim — Fri, 19 Sep 2008 14:13:39 +0000

I like your test list generator – thanks for making it. I also wish that MSTest had the NUnit category attribute.
http://timstall.dotnetdevelopersjournal.com/getting_categories_for_mstest_just_like_nunit.htm

Comment on Parsing Command Line Arguments by tihobrazov

tihobrazov — Mon, 08 Sep 2008 17:23:02 +0000

NConsoler is an open source library that provides command line parser functionality based on attribute metadata attached to type.
Library is very easy to add and use in your application. NConsoler gives an ability to display help and validation messages without any line of code.

http://nconsoler.csharpus.com/

Example code:

using System;
using NConsoler;

public class Program {
public static void Main(params string[] args) {
Consolery.Run(typeof(Program), args);
}

[Action]
public static void Method(
[Required] string name,
[Optional(true)] bool flag) {
Console.WriteLine(“name: {0}, flag: {1}”, name, flag);
}
}

and use it:

program.exe “Maxim” /-flag

Comment on Extending yourself… by Miles Thompson

Miles Thompson — Mon, 19 May 2008 21:03:47 +0000

Extension methods are indeed neat. And this is a clear example, but in this case I think overkill.

With .Net 3.5 compilation enabled, and this extension method defined, one can get the string valued ‘name’ of an enum, thus..

role.GetName();

On the other hand back in 2.0 world we managed to get by with..

role.ToString();

Which I think you’ll find produces the exact same output.

Comment on Parsing Command Line Arguments by Jay Cornwall

Jay Cornwall — Mon, 05 May 2008 18:35:56 +0000

Oh, I see! I skimread your post a bit too quickly, it seems.

I’ll give Andrew a bell.

Comment on Parsing Command Line Arguments by Shaun McCarthy

Shaun McCarthy — Mon, 05 May 2008 14:25:27 +0000

Credit where credit is due – I wasn’t actually the person who wrote the library – just wanted to point it out and give people a headstart with using it

Andrew Robinson is the person you should be thanking! You can probably contribute your patch to the following sourceforge project:

http://sourceforge.net/projects/csharpoptparse/

Comment on Parsing Command Line Arguments by Jay Cornwall

Jay Cornwall — Mon, 05 May 2008 12:58:40 +0000

Thanks for this library, I’ve found it really useful.

Here’s a small patch to allow the common case on Linux of passing arguments like this:
myprogram –dir /tmp

The current code sees this as incorrectly trying to mix UNIX and Windows style flags. This patch looks at the current OptStyle and allows values accordingly.

http://www.jcornwall.me.uk/patches/csharpoptparse/CSharpOptParse.patch

Comment on Parsing Command Line Arguments by Shaun McCarthy

Shaun McCarthy — Wed, 23 Apr 2008 15:23:27 +0000

Yup – it defaults to unix style – you can set it explicitly on the parser object:

p.OptStyle = OptStyle.Unix; // OptStyle.Windows

To support the debug flag:

[UseNameAsLongOption(false)]
[ShortOptionName('d')]
[OptDef(OptValType.Flag)] <- this is the magic source
[LongOptionName("debug")]
public bool Debug = false;

As for the date, either just keep it as a string, or parse it on the fly into another property:

[UseNameAsLongOption(false)]
[LongOptionName("date")]
[OptDef(OptValType.ValueReq)]
public string DateUnparsed
{
set
{
try
{
this.Date = DateTime.Parse(value);
}
catch (FormatException ex)
{
throw new ParseException(“Unable to parse the date value: ” + value, ex);
}
}
get
{
return “”;
}
}

public DateTime Date;

Then you just need to go arguments.Date to get the date (nb: the above code would fail with your date as it’s not a valid DateTime.Parse format – 2008/03/10 would work fine though)