Databases
StackOverflow2013
Postsdbo
POParsing an "advanced" INI file with PHP
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POParsing an "advanced" INI file with PHP
    primarykey
    data
    text
    <p>Basically, I would like a simple, easy, one-file way to parse an INI file with "advanced" features, like section inheritance and property nesting, like <a href="http://framework.zend.com/manual/en/zend.config.adapters.ini.html" rel="noreferrer">Zend_Config_Ini</a>.</p> <p>For example:</p> <pre><code>[foo] a = 1 b.a = 2 b.b = 3 b.c = 4 c = 5 [bar : foo] b.b = 17 c = 42 </code></pre> <p>Would parse into</p> <pre><code>array( 'foo'=&gt;array( 'a'=&gt;'1', 'b'=&gt;array( 'a'=&gt;'2', 'b'=&gt;'3', 'c'=&gt;'4' ), 'c'=&gt;'5' ), 'bar'=&gt;array( 'a'=&gt;'1', 'b'=&gt;array( 'a'=&gt;'2', 'b'=&gt;'17', 'c'=&gt;'4' ), 'c'=&gt;'42' ) ) </code></pre> <p>PHP's built-in <code>parse_ini_file</code>, doesn't handle anything other than simple INI's with simple sections and simple keys.</p> <p>My problem with using <code>Zend_Config_Ini</code> is that I would have to include virtually the whole Zend_Config subpackage, and is super-bloated and configurable.</p> <p><strong>Is there a <em>small</em> and <em>simple</em> library available to parse this?<br> If not, is there an <em>easy</em> implementation I'm not seeing?</strong></p> <p>By small and simple, I mean something like the sfYaml of INI files.</p> <p>To my (very inexperienced) eyes, I would have to parse through once with <code>parse_ini_file</code>, then come back and resolve inheritance, then run through each section and expand the keys recursively...</p> <p><strong>UPDATE</strong>: Since this seems to be a popular question, I would like to note that <a href="https://github.com/austinhyde/IniParser" rel="noreferrer">I have a simple class implementing this on GitHub</a>, feel free to send pull requests, issues, etc.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAustin Hyde
    1. USAustin Hyde
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POParsing an "advanced" INI file with PHP
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POParsing an "advanced" INI file with PHP
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POParsing an "advanced" INI file with PHP
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCan you explain why Zend_Config_* is "super bloated"? Oh, and you don't need the entire tree... Just Zend_Config, Zend_Config_Exception and Zend_Exception
      singulars
      1. POParsing an "advanced" INI file with PHP
      1. USJani Hartikainen
    2. COLooking through the source file, Zend_Config_Ini depends on Zend_Config_Exception and Zend_Config. Zend_Config_Exception depends on Zend_Exception. All the functionality is spread out over several classes and files. Granted, I hold ZF in *very* high regard for its OOP design, but in this case it really is too much.
      singulars
      1. POParsing an "advanced" INI file with PHP
      1. USAustin Hyde
    3. COAll I want it to do is to parse an ini to an associative array. I don't want or need the extra functionality that Zend_Config has.
      singulars
      1. POParsing an "advanced" INI file with PHP
      1. USAustin Hyde
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload