view release on metacpan or  search on metacpan

README  view on Meta::CPAN

    dynamically generated, and almost all with very short names.

    I wanted a way to organize the parameters, to make it easier to set up
    some simple guidelines for how to maintain parameters, and how to make
    sure they were accessable in a consistent manner. I decided to use a
    hierarchical, dot-delimited convention similar to what you seen in some
    programming languages. Now if I see a parameter like:

    /my.cgi?gbrowse.param.navigation.instructions=1

    I can pretty quickly guess, after not looking at the code for
    days/weeks/months, that this value is somehow affecting the instructions
    on the Gbrowse navigation page. In my opinion, this is superior to:

    /my.cgi?ins=0

    which had the same effect in an earlier version of the code (negated
    logic :o).

SEE ALSO
    CGI, Symbol

lib/CGI/ParamComposite.pm  view on Meta::CPAN

passed, some of them dynamically generated, and almost all with very short names.

I wanted a way to organize the parameters, to make it easier to set up some simple
guidelines for how to maintain parameters, and how to make sure they were accessable
in a consistent manner.  I decided to use a hierarchical, dot-delimited convention
similar to what you seen in some programming languages.  Now if I see a parameter
like:

  /my.cgi?navigation.instructions=1

I can pretty quickly guess, after not looking at the code for days/weeks/months, that
this value is somehow affecting the instructions on the Gbrowse navigation page.  In
my opinion, this is superior to:

  /my.cgi?ins=0

which had the same effect in an earlier version of the code (negated logic :o).

=head1 SEE ALSO

L<CGI>