On Fri, Oct 10, 2008 at 7:43 AM, via RT Florian Hatat <[EMAIL PROTECTED]> wrote: > The diff on the code itself is actually quite small: it was mainly a > matter of moving some code around, and adding the unique identifier > instead of the "$optable" static name. It contains an update for > docs/pct/pct_optable_guide.pod as well. It was made against the 0.7.1 > sources.
I'm not an expert on this area, but do we lose introspection on the optable object if they are all uniquely named? That is, if we want to modify one of the optables at runtime, are we going to be able to do it? Instead of simply giving all optables a unique identifier, maybe we should add them to a hash with the name of the "is optable" rule being the key for it. That way we could get to the various optables by name. Languages like Perl6 that expect to only have one optable could simply bind the preferred one to the "$optable" variable. --Andrew Whitworth
