You probably don't want to be using the symbolic references to be doing this, they are generally considered evil and unnecessary in most applications. Instead you probably want to be using a hash - something like: 

$element_count=0;
my %CLIQUE_DETAILS;
foreach $element (@CLIQUE_ID_START_LINES) {
if ($element !=  $CLIQUE_ID_START_LINES[$#CLIQUE_ID_START_LINES]) {
      for ($i = $element; $i<=$CLIQUE_ID_START_LINES[$element_count+1]
+; $i++) {
        if ( not exists $CLIQUE_DETAILS{$element_count} )
         {
            $CLIQUE_DETAILS{$element_count} = [];
         }
        push(@{$CLIQUE_DETAILS{$element_count}}, $VCONFIG[$i]);
        }
      $element_count++
}

[download]
Of course that is untested as I don't have your data.

/J\

In reply to Re: variable array names by gellyfish
in thread variable array names by Makarczyk

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.