This seems to work pretty well, except that it seems to get stuck when it parses into the next rule. I realized that I could have expanded my data example a bit. The rules I am trying to parse are sequential in the larry{} section. While your code works awesome, it seems to trip up just a little when encountering the next rule. Output example with my updated example above... 
{
  bob => {
           ed => {
                   larry => {
                     rule5 => {
                       "action"             => "allow",
                       "application"        => "[ any ]",
                       "category"           => "[ any ]",
                       "destination"        => "[ any ]",
                       "from"               => "[ prod-L3 ]",
                       "hip-profiles"       => "[ any ]",
                       "log-end"            => "yes",
                       "log-setting"        => "orion_log",
                       "log-start"          => "no",
                       "negate-destination" => "no",
                       "negate-source"      => "no",
                       "option"             => {
                                                 "action"             
+                => "allow",
                                                 "application"        
+                => "[ any ]",
                                                 "category"           
+                => "[ any ]",
                                                 "destination"        
+                => "[ any ]",
                                                 "disable-server-respo
+nse-inspection" => "no",
                                                 "from"               
+                => "[ prod-L3 ]",
                                                 "hip-profiles"       
+                => "[ any ]",
                                                 "log-end"            
+                => "yes",
                                                 "log-setting"        
+                => "orion_log",
                                                 "log-start"          
+                => "no",
                                                 "negate-destination" 
+                => "no",
                                                 "negate-source"      
+                => "no",
                                                 "service"            
+                => "[ any ]",
                                                 "source"             
+                => "[ any ]",
                                                 "source-user"        
+                => "[ any ]",
                                                 "to"                 
+                => "[ corp-L3 ]",
                                                 "}"                  
+                => "rule6 {  \n                opt
ion {  \n                    disable-server-response-inspection no",
                                               },
                       "service"            => "[ any ]",
                       "source"             => "[ any ]",
                       "source-user"        => "[ any ]",
                       "tag"                => "[ some_tag ]",
                       "to"                 => "[ corp-L3 ]",
                     },
                   },
                 },
         },
}

[download]

In reply to Re^2: Parsing a config file with braces and nested braces by IamtheGorf
in thread Parsing a config file with braces and nested braces by IamtheGorf

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.