My gut instinct is to store the user identity in a file associated with a number. When the questionnaire has been validated, delete the line that contains the translation. This of course requires that the adminstrator of the script is scrupulous and does not view the file that associates number to user. This is a simple way to handle it, and may or may not be feasible in a RL situation, but you've already said it's for a class, so in lieu of cookies, that's another option. This is known as storing persistent data, and while it's not exactly the cookbook way, it's under the same idea. (ie - read this to mean, go reread the Perl Cookbook aka the Ram)

As for your questionN -> N. You could duplicate the data from CGI.pm and set it up so that:

Update: The code here is flawed, see Re: Re: Re: Urgent help needed by inexperienced programmers to understand why. 

@params = $q->param();  # assuming using OO style of CGI.pm
foreach $val @params
{
  if ($val =~ /^question(.+)/)
  { $$1 = $q->param($val); }
}

[download]

and now they are accesible via just N, well $N to be fair.

Stick around, and you may see better answers. Remember this is just what first came to my mind.

ALL HAIL BRAK!!!

In reply to Re: Urgent help needed by inexperienced programmers by PsychoSpunk
in thread Urgent help needed by inexperienced programmers by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.