win32-mmap 0.2.4 → 0.3.0

data/CHANGES

@@ -1,9 +1,10 @@
+== 0.3.0 - 10-Apr-2013
+* Converted code to use FFI.
+
 == 0.2.4 - 28-Apr-2010
 * The Rakefile was refactored. It now handles gem creation, building and
   cleanup.
 * Inline code was removed from the gemspec.
-* Removed the doc directory from the repository. The information that was
-  there is already covered in the README.
 
 == 0.2.3 - 12-Aug-2009
 * Changed license to Artistic 2.0.

data/README

@@ -1,65 +1,64 @@
 = Description
-  This package provides a Ruby interface for memory mapped I/O on MS Windows.
+   This package provides a Ruby interface for memory mapped I/O on MS Windows.
    
 = Prerequisites
-  Ruby 1.8.2 or later.
-  windows-pr, 0.5.5 or later.
+   windows-pr, 0.5.5 or later.
 
 = Installation
-  gem install win32-mmap
+   gem install win32-mmap
    
 = Synopsis
-  require 'win32/mmap'
-  include Win32
+   require 'win32/mmap'
+   include Win32
    
-  map1 = MMap.new(:file => "C:\\test.map", :size => 1024)
-  map1.foo = 'hello'
-  map1.bar = 77
-  map1.close
+   map1 = MMap.new(:file => "C:\\test.map", :size => 1024)
+   map1.foo = 'hello'
+   map1.bar = 77
+   map1.close
    
-  map2 = MMap.new(:file => "C:\\test.map")
-  p map2.foo # 'hello'
-  p map2.bar # 77
-  map2.close
+   map2 = MMap.new(:file => "C:\\test.map")
+   p map2.foo # 'hello'
+   p map2.bar # 77
+   map2.close
 
 = About Memory Mapped Files under Windows
-  Under Windows, code and data are both repesented by pages of memory backed
-  by files on disk, code by executable image and data by system pagefile
-  (i.e. swapfile). These are called memory mapped files. Memory mapped files
-  can be used to provide a mechanism for shared memory between processes.
-  Different processes are able to share data backed by the same swapfile,
-  whether it's the system pagefile or a user-defined swapfile.
+   Under Windows, code and data are both repesented by pages of memory backed
+   by files on disk, code by executable image and data by system pagefile
+   (i.e. swapfile). These are called memory mapped files. Memory mapped files
+   can be used to provide a mechanism for shared memory between processes.
+   Different processes are able to share data backed by the same swapfile,
+   whether it's the system pagefile or a user-defined swapfile.
 
-  Windows has a tight security system that prevents processes from directly
-  sharing information among each other, but mapped memory files provide a
-  mechanism that works with the Windows security system by using a name that
-  all processes use to open the swapfile.
+   Windows has a tight security system that prevents processes from directly
+   sharing information among each other, but mapped memory files provide a
+   mechanism that works with the Windows security system by using a name that
+   all processes use to open the swapfile.
 
-  A shared section of the swapfile is translated into pages of memory that are
-  addressable by more than one process, Windows uses a system resource called a
-  prototype page table entry (PPTE) to enable more than one process to address
-  the same physical page of memory, thus multiple process can share the same
-  data without violating the Windows system security.
+   A shared section of the swapfile is translated into pages of memory that are
+   addressable by more than one process, Windows uses a system resource called a
+   prototype page table entry (PPTE) to enable more than one process to address
+   the same physical page of memory, thus multiple process can share the same
+   data without violating the Windows system security.
 
-  In short, memory mapped files provide shared memory under Windows.
+   In short, memory mapped files provide shared memory under Windows.
 
-  (This explanation was largely borrowed from Roger Lee's Win32::MMF Perl
-  module.)
+	(This explanation was largely borrowed from Roger Lee's Win32::MMF Perl
+	module.)
 
 = Future Plans
-  Suggestions welcome.
+   Suggestions welcome.
 
 = License
-  Artistic 2.0
+   Artistic 2.0
     
 = Copyright
-  (C) 2003-2010 Daniel J. Berger, All Rights Reserved
+   (C) 2003-2013 Daniel J. Berger, All Rights Reserved
     
 = Warranty
-  This package is provided "as is" and without any express or
-  implied warranties, including, without limitation, the implied
-  warranties of merchantability and fitness for a particular purpose.
+   This package is provided "as is" and without any express or
+   implied warranties, including, without limitation, the implied
+   warranties of merchantability and fitness for a particular purpose.
     
 = Authors
-  Daniel J. Berger
-  Park Heesob
+   Daniel J. Berger
+   Park Heesob

data/Rakefile

@@ -1,12 +1,10 @@
 require 'rake'
+require 'rake/clean'
 require 'rake/testtask'
 
-namespace 'gem' do
-  desc 'Delete any gem files in the project.'
-  task :clean do
-    Dir['*.gem'].each{ |f| File.delete(f) }
-  end
+CLEAN.include('**/*.gem')
 
+namespace 'gem' do
   desc 'Create the win32-mmap gem.'
   task :create => [:clean] do
     spec = eval(IO.read('win32-mmap.gemspec'))
@@ -41,3 +39,5 @@ Rake::TestTask.new do |t|
   t.verbose = true
   t.warning = true
 end
+
+task :default => :test