in reply to Re: CGI fails to urlencode & chars in outbound url's
in thread CGI fails to urlencode & chars in outbound url's

Thanks. Exactly what I needed.

Without going into long explanations of Perl internals, is there a reason this has been implemented as:

use URI::Escape; $encoded = uri_escape($unsafe_uri);

instead of as (what seems to me would more intuative (and easier to find))

use URL qw( urlencode ); $encoded = urlencode( $unsafe_uri );

Or is this a simple case of "Thats the way the author chose to do it"?

Replies are listed 'Best First'.
Re(3): CGI fails to urlencode & chars in outbound url's
by cjf (Parson) on Jun 12, 2002 at 11:37 UTC
    Or is this a simple case of "Thats the way the author chose to do it"?

    Pretty much. The author of a module can name it whatever they want to. Whether or not CPAN allows them to upload it under that name is a different issue (you can probably find the answer in The CPAN Faq).

    As for why the URI module was named URI instead of URL, there is a slight difference between the two. More information on this is available here.