use Perl

• Reply (Score:1)

  by cosine (8058)

  I think your aversion to eval is a mistake, but if it is not then you are not going to convince me with your current line of thought. I posted my reply: http://www.cosine.org/2007/08/16/languagepowered-domain-specific-language/ [cosine.org]
  • Re: (Score:1)

    by Aristotle (5147)

    How am I supposed to argue with your example? You showed a design wherein a class reads a config file every time it is instantiated. I have no idea how that can be construed as useful; the fact that you use eval is incidental and at best draws attention away from the fact that you are reading a config file on every instantiation. After all, “the config file is code!” Do you really need to recompile the code every time someone makes an instance of it? Sorry, that example just doesn’t cut i
    • Re:Reply (Score:1)

      by cosine (8058) on 2007.08.16 13:53 (#57023)

      I'll just take this to mean we still have irreconcilable differences in our opinions here. :) I appreciate the time you took to respond.

      Reply to This

      Parent

      • Re: (Score:1)

        by Aristotle (5147)

        Basically my opinion is that anyone who thinks Perl, Python and Ruby differ in any sort of significant fashion hasn’t seen a lot of languages. The three are close to identical. Sure, there are lots and lots of superficial differences – they optimise in different directions, and that is what ends up making me prefer Perl and you Ruby and still others Python. But their fundamental premises are completely identical so there is no substantial difference in terms of expressiveness, overall. Ruby wins