Paul LeoNerd Evans wrote:
No, I think at this point we have to appeal to the core reason for
creating this module in the first place; namely, that it is
bidirectional. Parsing a string into variables, or interpolating the
variables back into a string. Both can be done within one object,
symmetrically. To introduce something that breaks that symmetry
effectively removes the requirement that it be done within one
object, at
which point one might as well use two separate objects for each
individual
operation.
If the main objects your module will manipulate still are URIs, maybe
it should be in the URI:: namespace. And couldn't the bidirectional
relation you want to create be seen like a mapping? Hence URI::Mapper
or something similar?
--
Sébastien Aperghis-Tramoni
Close the world, txEn eht nepO.
