On 10/5/05, Peter Speltz <[EMAIL PROTECTED]> wrote: > Ok. I checked this out. Nice work Dave. Beutiful docs and formatting > and style. It was very easy to read. For core interface , i was just > thinking of a simpel make_uri method. > to be parse_paths other half.
I think the counterpart to parse_path() should be called make_path(). LinkTools has a make_path() (but it's poorly implemented ATM because it doesn't use URI). make_path() should probably return a string, rather than a URI object, because I've found a few CPAN modules out there will choke on objects even if the object has a perfectly good stringification behaviour. So I'd suggest adding a make_path to Path-URI, with the same interface as make_uri (which it'll call internally). LinkTools::make_path takes named params, whereas Path::URI::make_uri takes positional args. It would be nice if we could combine the two. I'd like to see this in core, because then we can document path making and URL parsing in the same place, and emphasize the advantages of using these methods for all path manipulation. Also, there's the potential for make_path and parse_path to both use a shared path template, so the whole path scheme could be changed at a single point. d. ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Maypole-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/maypole-devel
