in reply to Re: Comparing Perl with C#, a simple templating example
in thread Comparing Perl with C#, a simple templating example

"I probably won't live long enough to ever have to program in C#"

Try it at least once, at least I will ;-)

As a matter of fact, one of our GUI user interface needs to be totally rewritten becaue of the user requirement changed. I am looking at C#, it was in Open Road (an engres thingy).

BTW, for most of the application areas, C# is not targetting any thing else, but Java. GUI application is a good candidator to try C# with, because of the IDE. I took a look at the way C# defines event, handles event are quite interesting. C# even tries to beat Java with small things like how to define getters and setters.

Perl should not be the one feels the most pressure from C#. For example, in this case, as a GUI interface thing, at least from my point of view, Perl is not a candidator any way.

  • Comment on Re^2: Comparing Perl with C#, a simple templating example

Replies are listed 'Best First'.
Re^3: Comparing Perl with C#, a simple templating example
by simon.proctor (Vicar) on Oct 18, 2004 at 09:03 UTC
    C# even tries to beat Java with small things like how to define getter +s and setters.
    Thats just syntactic sugar. You may be able to use "properties" but in essence they just get re-written to the underlying subroutines anyway. Of course if you use code completion incorrectly you can get bitten :). Here's some recursive property code just for fun.
    using System; public class MyClass { private string person = ""; public string Person { set { this.Person = value; } get { return this.person; } } public static void Main() { MyClass app = new MyClass(); app.run(); } public void run() { string temp = "temp"; // Crash me this.Person = temp; } }
    Though I confess writing your own array accessor for an object is nice.