> This is a slightly more compact form of what is already proposed. It > has a similar upside with a similar downside. In your design, you > could add to the EXPRESSION_LITERALIZERS array for new objects, but I > think the differences in arity among the methods makes your design a > bad idea.
What's the downside to requiring each literalizing method to take the expression as the first and only argument? We basically just want to mimic what we'd get in a language with multiple dispatch -- calling one of a family of member function based on the runtime type of the argument. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en -~----------~----~----~----~------~----~------~--~---
