Comment Feed for Help Related to CSharp Coding (TechOff on Channel 9)

Re: Re: Re: Re: Re: Help Related to CSharp Coding

cheong — Tue, 13 Jan 2009 05:33:26 GMT

I don't know about it. Thanks for telling me. (I've learnt to evade from names that I believe to be error_prone when coding, so haven't got chance to see it before.)

But this doesn't prevent the name be a poor choice, does it? ;)

Re: Re: Re: Re: Help Related to CSharp Coding

Ion Todirel — Tue, 13 Jan 2009 03:30:03 GMT

Yes, but C# is compiled to IL (like other managed languages does too), it's not like you'll use the C# source file directly in VB, you'll use the compiled assembly, in which the "operators" are converted to methods with op_%special_name% name format (and I don't imagine the compiler teams will change the name it in such a way that it will break if you use Operator), and thats what languages like VB or others use. Just saying.... :)

Re: Re: Re: Help Related to CSharp Coding

cheong — Tue, 13 Jan 2009 03:02:13 GMT

True (otherwise C# won't let him compile it) but it IS a keyword in case insensitive languages like VB.NET. (That's the reason I said "in the future")

Someone writing programs that add reference to your module will probably thank him for this... and I suspect there's other similar poorly chosen names hiding in the modules...

Re: Re: Help Related to CSharp Coding

Ion Todirel — Tue, 13 Jan 2009 02:30:55 GMT

Operator is not a keyword, operator is

Re: Help Related to CSharp Coding

cheong — Mon, 12 Jan 2009 09:26:11 GMT

// Offender suspect from Operator.drawHistogram()

form.pb_color.Image = bmp;

I'd advise remove all reference to Form1 in Operator class before debugging...

P.S.: Something deep inside me have a feeling that naming a class with a keyword is asking for trouble in the future...