Re: [pclasses-devel] where to put these classes?

[Marc D. <bdu...@gm...>]

The STL has ext for this. Would you like something like P::Ext?

Marc

On Saturday 25 Dec 2004 21:36, stephan beal wrote:
> Hiya!
>
> i've got some string utility code i'd like to bring in to support the
> App module, and i'm not sure where to put it. Basically it is these
> functions:
>
> - generic entity un/expansion algos for use with, e.g. HTML, XML. Used
> extensively by s11n's file parsers.
> - lexical casting API (this code existed long before Util::LexT did).
> - perl-like split() and join().
>
> i'd also like to move the $VAR expansion code there, as i can implement
> it in terms of the entity expansion code, which means it won't be
> specific to Environment.
>
> Anyway, some ideas about where to put this:
>
> - Util
> - new module, but don't call it String or Util::String, to avoid
> confusion with Unicode::String. Don't call it Str, because that could
> also mean Stream.
> - Exp (is that were Regex goes bzw will go?)
> - new module, P::UseAtOwnRisk
> - new module, P::Foo
>
> Where to put it? These are important for the App bzw ShellApp code, so
> i'd like to get them pulled in, renamed, etc.
>
> Speaking of regex: reimplementing the entity expansion routines using
> Regex would be cool.
>
>
> ???