--- !ruby/object:Gem::Specification
name: inifile
version: !ruby/object:Gem::Version
  version: 1.0.0
  prerelease: 
platform: ruby
authors:
- Tim Pease
autorequire: 
bindir: bin
cert_chain: []
date: 2012-02-28 00:00:00.000000000Z
dependencies:
- !ruby/object:Gem::Dependency
  name: bones-git
  requirement: &2157141580 !ruby/object:Gem::Requirement
    none: false
    requirements:
    - - ! '>='
      - !ruby/object:Gem::Version
        version: 1.2.5
  type: :development
  prerelease: false
  version_requirements: *2157141580
- !ruby/object:Gem::Dependency
  name: bones
  requirement: &2157140760 !ruby/object:Gem::Requirement
    none: false
    requirements:
    - - ! '>='
      - !ruby/object:Gem::Version
        version: 3.7.2
  type: :development
  prerelease: false
  version_requirements: *2157140760
description: ! "Although made popular by Windows, INI files can be used on any system
  thanks\nto their flexibility. They allow a program to store configuration data,
  which\ncan then be easily parsed and changed. Two notable systems that use the INI\nformat
  are Samba and Trac.\n\nMore information about INI files can be found on the [Wikipedia
  Page](http://en.wikipedia.org/wiki/INI_file).\n\n### Properties\n\nThe basic element
  contained in an INI file is the property. Every property has\na name and a value,
  delimited by an equals sign *=*. The name appears to the\nleft of the equals sign
  and the value to the right.\n\n    name=value\n\nAll properties must exist within
  a section. If the file contains a property\nbefore the first section is declared,
  an error will be raised.\n\n### Sections\n\nSection declarations start with *[*
  and end with *]* as in `[section1]` and\n`[section2]` shown in the example below.
  The section declaration marks the\nbeginning of a section. All properties after
  the section declaration will be\nassociated with that section.\n\n### Comments\n\nAll
  lines beginning with a semicolon *;* or a number sign *#* are considered\nto be
  comments. Comment lines are ignored when parsing INI files.\n\n### Example File
  Format\n\nA typical INI file might look like this:\n\n    [section1]\n    ; some
  comment on section1\n    var1 = foo\n    var2 = doodle\n    var3 = multiline values
  \\\n    are also possible\n\n    [section2]\n    # another comment\n    var1 = baz\n
  \   var2 = shoodle"
email: tim.pease@gmail.com
executables: []
extensions: []
extra_rdoc_files:
- History.txt
files:
- .gitignore
- History.txt
- README.md
- Rakefile
- lib/inifile.rb
- test/data/bad_1.ini
- test/data/bad_2.ini
- test/data/browscap.ini
- test/data/comment.ini
- test/data/escape.ini
- test/data/good.ini
- test/data/merge.ini
- test/data/mixed_comment.ini
- test/data/multiline.ini
- test/data/param.ini
- test/test_inifile.rb
homepage: http://rubygems.org/gems/inifile
licenses: []
post_install_message: 
rdoc_options:
- --main
- README.md
require_paths:
- lib
required_ruby_version: !ruby/object:Gem::Requirement
  none: false
  requirements:
  - - ! '>='
    - !ruby/object:Gem::Version
      version: '0'
required_rubygems_version: !ruby/object:Gem::Requirement
  none: false
  requirements:
  - - ! '>='
    - !ruby/object:Gem::Version
      version: '0'
requirements: []
rubyforge_project: inifile
rubygems_version: 1.8.11
signing_key: 
specification_version: 3
summary: INI file reader and writer
test_files:
- test/test_inifile.rb