--- !ruby/object:Gem::Specification 
name: inifile_alt
version: !ruby/object:Gem::Version 
  hash: 11
  prerelease: 
  segments: 
  - 2
  - 0
  - 2
  version: 2.0.2
platform: ruby
authors: 
- Tim Pease
autorequire: 
bindir: bin
cert_chain: []

date: 2013-03-14 00:00:00 Z
dependencies: 
- !ruby/object:Gem::Dependency 
  name: bones-git
  prerelease: false
  requirement: &id001 !ruby/object:Gem::Requirement 
    none: false
    requirements: 
    - - ">="
      - !ruby/object:Gem::Version 
        hash: 3
        segments: 
        - 0
        version: "0"
  type: :development
  version_requirements: *id001
- !ruby/object:Gem::Dependency 
  name: bones
  prerelease: false
  requirement: &id002 !ruby/object:Gem::Requirement 
    none: false
    requirements: 
    - - ">="
      - !ruby/object:Gem::Version 
        hash: 39
        segments: 
        - 3
        - 8
        - 0
        version: 3.8.0
  type: :development
  version_requirements: *id002
description: |-
  Although made popular by Windows, INI files can be used on any system thanks
  to their flexibility. They allow a program to store configuration data, which
  can then be easily parsed and changed. Two notable systems that use the INI
  format are Samba and Trac.
  
  More information about INI files can be found on the [Wikipedia Page](http://en.wikipedia.org/wiki/INI_file).
  
  ### Properties
  
  The basic element contained in an INI file is the property. Every property has
  a name and a value, delimited by an equals sign *=*. The name appears to the
  left of the equals sign and the value to the right.
  
      name=value
  
  ### Sections
  
  Section declarations start with *[* and end with *]* as in `[section1]` and
  `[section2]` shown in the example below. The section declaration marks the
  beginning of a section. All properties after the section declaration will be
  associated with that section.
  
  ### Comments
  
  All lines beginning with a semicolon *;* or a number sign *#* are considered
  to be comments. Comment lines are ignored when parsing INI files.
  
  ### Example File Format
  
  A typical INI file might look like this:
  
      [section1]
      ; some comment on section1
      var1 = foo
      var2 = doodle
      var3 = multiline values \
      are also possible
  
      [section2]
      # another comment
      var1 = baz
      var2 = shoodle
email: tim.pease@gmail.com
executables: []

extensions: []

extra_rdoc_files: []

files: 
- .idea/.name
- .idea/.rakeTasks
- .idea/compiler.xml
- .idea/encodings.xml
- .idea/misc.xml
- .idea/modules.xml
- .idea/scopes/scope_settings.xml
- .idea/uiDesigner.xml
- .idea/vcs.xml
- .idea/workspace.xml
- .travis.yml
- History.txt
- README.md
- Rakefile
- inifile.iml
- lib/inifile.rb
- test/data/bad_1.ini
- test/data/browscap.ini
- test/data/comment.ini
- test/data/escape.ini
- test/data/global.ini
- test/data/good.ini
- test/data/merge.ini
- test/data/mixed_comment.ini
- test/data/multiline.ini
- test/data/no_escaping.ini
- test/data/param.ini
- test/test_inifile.rb
homepage: http://rubygems.org/gems/inifile
licenses: []

post_install_message: 
rdoc_options: []

require_paths: 
- lib
required_ruby_version: !ruby/object:Gem::Requirement 
  none: false
  requirements: 
  - - ">="
    - !ruby/object:Gem::Version 
      hash: 3
      segments: 
      - 0
      version: "0"
required_rubygems_version: !ruby/object:Gem::Requirement 
  none: false
  requirements: 
  - - ">="
    - !ruby/object:Gem::Version 
      hash: 3
      segments: 
      - 0
      version: "0"
requirements: []

rubyforge_project: inifile_alt
rubygems_version: 1.8.24
signing_key: 
specification_version: 3
summary: INI file reader and writer
test_files: 
- test/test_inifile.rb