Okay. Have a better appreciation of your constraints. Have played around with your code a bit and I think it covers all of the cases that you showed well. There may be a bit of an opportunity to make the config file syntax a little less visually cluttered though.

If you can trust that there are empty lines between the blocks and not within, you can strip off the need for the > or < symbols at the start of each line. Also if you just assume an empty selector means >, then you only have to place the < selectors in cases where you don't want to nudge the index forward. Check out the example DATA below the code. The code will still parse your original example as well if you don't like these changes.

All bugs are mine after twisting your code around like this:

use strict;
use warnings;
use Data::Diver  qw( DiveVal DiveError );
use Data::Dumper qw( Dumper );

my $state = { };
my $ref   = [ ];
my $prefix = '<';

while (<DATA>) {
    chomp;
    next if /^\s*#.*$/;
    if (/^\s*$/) {
            $prefix = '>';
            next;
    };
    my ($selector, $value) = split /\s*=\s*/;
    next unless defined $selector;
    my @selector = split /\./, $selector =~ s/\.$/.>/r;
    unshift(@selector, $prefix) unless $selector =~ /^[><]\./;
    _dive( $ref, \@selector, $value );
    $prefix = '<';
}

print Dumper $ref;

sub _dive
{
    my ( $ref, $selector, $value ) = @_;

    return unless defined $ref and defined $selector and scalar @$sele
+ctor;

    my @selector_b;
    for ( @$selector ) {
        if ( /^(>|<|)$/ ) {
            my $selector_b = join '.', @selector_b;
            if ( $1 eq '<') {
                push @selector_b, $state->{$selector_b} //= 0;
            } else {
                $state->{$selector_b} += defined $state->{$selector_b}
+ ? 1 : 0;
                push @selector_b, $state->{$selector_b};
            }
        } else {
            push @selector_b, $_;
        }
    }

    DiveVal( $ref, @selector_b ) = $value;
    my ( $error ) = DiveError( );
    $error and warn $error;

    return 1;
}
__DATA__

name          = john
location      = uk
interests.    = programming
interests.    = cycling

name          = laura
location      =
interests.    = knitting
interests.    = tennis
interests.    = dancing

name
location      = canada
interests..   = dogs
interests.<.  = horses
interests.    = cars

# test.error = blah

[download]

In reply to Re^3: Dive data with automatic array indexing by Loops
in thread Dive data with automatic array indexing by peterp

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.