On Wed, Mar 21, 2012 at 12:10 PM, Massimo Manghi <mxman...@apache.org> wrote: > On Wed, 2012-03-21 at 08:15 +0100, Harald Oehlmann wrote: >> Am 21.03.2012 00:10, schrieb Massimo Manghi: >> > On Wed, 2012-03-14 at 17:59 +0100, Harald Oehlmann wrote: >> >> I would try to stay as compatible to tcllib as possible: >> >> >> >> html::html_entities >> >> >> >> but this is not a really nice name. >> > >> > I would mark the difference between tcllib's implementation and Rivet's >> > adopted code. What if we get the code into a 'entitities' package and >> > let the actual command be placed within the ::rivet namespace? >> > >> > e.g. >> > >> > package require entities >> > set xformed_text [::rivet::entities $text] >> > >> > or >> > >> > ::rivet::html_entities >> >> I like both, but would prefer the first. >> > > Me too, but if 'entities' as subcommand doesn't make sense, we need a > also meaningful name for the inverse subcommand. > '::rivet::encode'/'rivet::decode' are excellent but too generic after > all. Suggestions? >
Although PHP is not necessarily the best thing to emulate, it does have the benefit of having a large established userbase and new Rivet users might have familiarity with its name choices. htmlentities -- http://php.net/htmlentities html_entity_decode -- http://php.net/html_entity_decode These two are basically the equivalents of Rivet's escape_string and unescape_string: urlencode -- http://php.net/urlencode urldecode -- http://php.net/urldecode --------------------------------------------------------------------- To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
