Skip to content

Commit

Permalink
resolve #195 - clarify HTML function non removal
Browse files Browse the repository at this point in the history
  • Loading branch information
leejo committed Jan 23, 2016
1 parent c9d3b28 commit ef41778
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 8 deletions.
4 changes: 0 additions & 4 deletions lib/CGI.pod
Expand Up @@ -137,8 +137,6 @@ For example, using the object oriented style:
my $q = CGI->new; # create new CGI object
print $q->header; # create the HTTP header

...

In the function-oriented style, there is one default CGI object that
you rarely deal with directly. Instead you just call functions to
retrieve CGI parameters, manage cookies, and so on. The following example
Expand All @@ -155,8 +153,6 @@ need to create the CGI object.
use CGI qw/:standard/; # load standard CGI routines
print header(); # create the HTTP header

...

The examples in this document mainly use the object-oriented style. See HOW
TO IMPORT FUNCTIONS for important information on function-oriented programming
in CGI.pm
Expand Down
6 changes: 2 additions & 4 deletions lib/CGI/HTML/Functions.pod
Expand Up @@ -6,10 +6,8 @@ CGI::HTML::Functions - Documentation for CGI.pm Legacy HTML Functionality

Nothing here - please do not use this functionality, it is considered to
be legacy and essentially deprecated. This documentation exists solely to
aid in maintenance and migration of legacy code using this functionality.

This functionality is likely to be removed in future versions of CGI.pm so
you are strongly encouraged to migrate away from it. If you are working
aid in maintenance and migration of legacy code using this functionality
and you are strongly encouraged to migrate away from it. If you are working
on new code you should be using a template engine. For more information see
L<CGI::Alternatives>.

Expand Down

0 comments on commit ef41778

Please sign in to comment.