nano 0.8.1

data/ANN-0.8.1

@@ -0,0 +1,127 @@
+
+DRUM ROLL PLEASE. I'm happy to announce two new sister projects: 
+Nano Methods and Mega Modules. They are born from the heritage of the
+old Ruby Facets project (now deprecated). In the course of the last 
+several months a slew of major improvements have been made. We have some
+spiffy new websites and, most importantly, this release marks the 
+beginning of a clear window toward 1.0 status.
+
+GREAT NEWS! Nano Methods and Mega Modules are now the official
+support libraries for Nitro and Og (http://www.nitrohq.com).
+Nitro is a sophisticated Web Application Engine and Og is an
+intuitive yet powerful Object Relational Mapping Library.
+
+WHY MEGA? You may have noticed that I back peddled on the major change to
+Facets 0.7.0. In that release I had merged the class and module additions
+library, Ruby Carats, into Facets. But I had to separate them out again. It 
+simply proved too cumbersome to have such a variety of content all in one
+location. I am very excited the re-separation though. It has already lent 
+itself to major improvements to the library, with a number of exciting 
+additions on the way.
+
+NANO SYSTEM. Another new feature is the introduction of the NanoSystem
+module. This module provides access to meta-info about Nano's extensions.
+Primarily it is an index of all the methods. With this information at its
+disposal another unique way to require method becomes possible:
+
+  require 'nanosys'
+
+  String.use :capitalized?, :underscore
+
+I am not recommending this approach at the moment. But in the long run,
+as the NanoSystem module matures, it may well prove to be a much more
+elegant means of extension loading.
+
+FOR FACETS USERS. To upgrade, the project name change will require
+you to change the #require path-space from 'facet/' to 'nano/', or 
+occasionally 'mega/'. The division is pretty clear, Nano stores methods
+and Mega stores classes and modules. Sorry for the inconvenience, but 
+after a long debate I decided it was worth it --and better to do so now
+rather then later. Hope you like the new names.
+
+CORNUCOPIA. Finally, there are also _a lot_ of minor changes in this release.
+Some of them are simply improvements in the naming of methods or more appropriate 
+class/module placement. I've gone over all the methods enough now to be
+confident that the present methods are pretty well set. You can expect many fewer
+name/location changes from here on out. Also, a good number of new methods have
+been added. Most of these I have managed to make mention of in the following
+ChangeLog summary.
+
+* Class methods are not prefixed with '::' to separate them from instance methods.
+
+* Added logger #format and #format_message (whomever wrote these please let me know,
+I got them thru a second-hand source and the original author is lost to me. I try
+very hard to credit where credit is due.)
+
+* Renamed object/supers to object/superup. Better!
+
+* Got rid of symbol/gen. Use object/generate_method_name or 
+module#generate_instance_method_name instead. [ed- Is that the longest
+non-foo method name ever?]
+
+* The file 1st.rb file has moved to object/method!. This provides a version
+of #method that persists the returned Method object.
+
+* Added module/clone_using, module/clone_renaming and module/clone_removing.
+
+* Added module/integrate (I love this one, but note that its syntax is not yet
+set in stone.)
+
+* Added many new enumerable methods: #filter_map, #compact_map, #commonality,
+#frequency, #probability and #find_collisions.
+
+* Moved some methods from array to enumerable: #each_permutation,
+#each_combination, #each_unique_pair and the class method ::combinations.
+
+* Added string/bytes per ruby-dev summary 26385-26467.
+
+* Moved #cattr_reader, #cattr_writer and #cattr_accessor from Class to Module.
+These are the class variable attributes as defined by Rails DHH.
+
+* Added class instance attribute methods: iattr_reader, iatter_writer, &c.
+The name of these are not set in stone. It's a bad misnomer. Looking
+for suggestions.
+
+* Added methods to comparable: #cap, #clip. #clip replaces #bound_by, since
+'by' generally indicates the method takes a block parameter. I have retained
+#at_least and #at_most, although #cap and #clip handle the same functionality.
+
+* Added class/descendants (alias subclasses) and class/remove_descendants.
+
+* Removed string/table_name and string/class_name (were too Rails specific).
+Note: A new module has been added to Mega Modules, called orm_inflect.rb. 
+It contains numerous methods for doing this sort of thing.
+
+* Added numeric/ceil_multiple.
+
+* Added string/soundex for calculating the soundex code of a word/name.
+
+* numeric/octet_units has bee moved to mega/binary_multipliers, which
+is a rewrite of Richard Kilmer's bytes.rb. Actually #octet_units is
+now just an alias or #strfbytes, accompanied by #strfbits.
+
+* Placed Florian's binding-of-caller.rb in binding/of_caller. Makes more
+sense there.
+
+* Fixed Continuation::create; it wasn't defined as a class method
+and should have been.
+
+* Fixed bug with string/capitalized? which wasn't always giving the correct
+result.
+
+There are a number of others, but this particular session of development was
+so rapid and choked full, I wasn't able to log them all. 
+Please see the API RDocs for a complete listing.
+
+CONTRIBUTE. As always, if you have any extension methods that you use and think
+may be of benefit to others, please submit them. There's a good chance they'll be
+incorporated. Also, if you happen to notice any code that is mis-credited or is
+not credited at all and should be, please correct me. Giving credit where credit 
+is due is _vry_ important to me, unfortuantely in the juggle of things it doesn't
+always get doen as wellas it should. And, of course, please let me know if you
+come across any bugs.
+
+You can contact me either privately or via ruby-talk.
+
+Thanks and Enjoy,
+trans|onoma

data/COPYING

@@ -0,0 +1,59 @@
+The Ruby License (http://www.ruby-lang.org/en/LICENSE.txt)
+----------------------------------------------------------
+
+You may redistribute this software and/or modify it under either the terms of
+the GPL (see the file GPL), or the conditions below:
+
+  1. You may make and give away verbatim copies of the source form of the
+     software without restriction, provided that you duplicate all of the
+     original copyright notices and associated disclaimers.
+
+  2. You may modify your copy of the software in any way, provided that
+     you do at least ONE of the following:
+
+       a) place your modifications in the Public Domain or otherwise
+          make them Freely Available, such as by posting said
+          modifications to Usenet or an equivalent medium, or by allowing
+          the author to include your modifications in the software.
+
+       b) use the modified software only within your corporation or
+          organization.
+
+       c) rename any non-standard executables so the names do not conflict
+          with standard executables, which must also be provided.
+
+       d) make other distribution arrangements with the author.
+
+  3. You may distribute the software in object code or executable
+     form, provided that you do at least ONE of the following:
+
+       a) distribute the executables and library files of the software,
+          together with instructions (in the manual page or equivalent)
+          on where to get the original distribution.
+
+       b) accompany the distribution with the machine-readable source of
+          the software.
+
+       c) give non-standard executables non-standard names, with
+          instructions on where to get the original software distribution.
+
+       d) make other distribution arrangements with the author.
+
+  4. You may modify and include the part of the software into any other
+     software (possibly commercial).  But some files in the distribution
+     are not written by the author, so that they are not under these terms.
+
+     For the list of those files and their copying conditions, see the
+     file LEGAL.
+
+  5. The scripts and library files supplied as input to or produced as
+     output from the software do not automatically fall under the
+     copyright of the software, but belong to whomever generated them,
+     and may be sold commercially, and may be aggregated with this
+     software.
+
+  6. THIS SOFTWARE 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.
+

data/ChangeLog

@@ -0,0 +1,137 @@
+--- !!history
+
+v0.8.1:
+- Added logger/format and logger/format_message.
+- Added string/dequote.
+- Class method file names now begin with '::' to separate them from instance methods.
+
+v0.8.0:
+- Name Change! What was Ruby Facets is now Nano Methods!
+- New minor version as there has been a change of plans with the integration of what was Carats.
+  The classes and modules have been reseperated into their own project called Mega Modules.
+- Modified the #firstxxx/#lastxxx methods to be more congruent and comprehensible.
+- Renamed object/supers to object/superup. Better!
+- Got rid ot symbol/gen. Use object/generate_method_name or  module#generate_instance_method_name
+  instead ( Is that the longest non-foo method name ever? :)
+- The file 1st.rb has moved to object/method. This modifies #method to persist the returned
+  Method object. The original non-persitent version of #method is aliased to #original_method.
+  (This arrangement is not set in stone though, and is still be considered.)
+- Added module/clone_using, module/clone_ranaming and module/clone_removing.
+- Added module/integrate (I love this one!)
+- Added many new enumerable methods: #filter_map, #compact_map, #commonality, #frequency,
+  #probability and #find_collisions.
+- Moved some methods from array to enumerable: #each_permutation, #each_combination, 
+  #each_unique_pair and the class method ::combinations.
+- Added string/bytes per ruby-dev summary 26385-26467.
+- Moved #cattr_reader, #cattr_writer and #cattr_accessor from Class to Module.
+- Renamed numeric/octet_units to numeric/bytes_to_s and added a #bits_to_s as well.
+- Added class/descendants (alias subclasses) and class/remove_descendents, as well as
+  object/descendents_of and object/remove_descendents_of.
+- Added methods to comparable: #cap, #clip. There are also #at_least and
+  #at_most, although FYI #cap and #clip handle the same functionality.
+- Removed string/table_name and string/class_name (they were too Rails specific).
+  Note: A new module has been added to Mega Modules, called orm-inflect.rb. It contains numerous
+  methods for doing this sort of thing.
+- Added numeric/ceil_multiple (not sure about name though, perhaps a better name like "ceil_to"?).
+- Added string/soundex for calculating the soundex code of a word/name.
+- Added io/expect. I thought Ruby already had this but can't find it, so here it is for now.
+- Placed Florian's binding-of-caller.rb in binding/of_caller. Makes more sense there.
+- Fixed bug with Continuation::create (it wasn't defined as a class method and should have been).
+- Fixed bug with string/capitalized? which wasn't always giving the correct result.
+
+v0.7.2:
+- Added a class method dir/recurse which allows one to loop through a dir and all its
+  subdirs, etc. It also has an alias #ls_r. Thanks goes to George Maschovitis for this.
+- Changed array/permute to array/each_permutation.
+
+v0.7.1:
+- Added facet.rb, although expiremental it makes it possible to use atomic methods without
+  specificaly requiring them. It uses Object#method_missing to require them as needed.
+- Improved on "molecules", i.e. files that require numerous related atoms in a single go.
+  These will see a great deal of continued improvement in the future.
+
+v0.7.0:
+- All methods with names containing non-alphanumeric characters now have facet
+  files without those special characters. This removes some incompatibilites with 
+  certain systems (including Windows). All such symbols have been replaced with
+  CGI escape sequences, for instance 'in?.rb' becomes 'in%3F.rb'. To avoid having
+  to use these "ugly" names, a new method has been added, kernel/require_facet.
+- Methods that were grouped together in the same file have been separated 
+  into their own files. Pure Atomicity has been achieved!
+- The method array/put has been dropped in favor of array/top (as a better alias for #unshift).
+- Methods #matchdata/post_match_from and #matchdata/pre_match_from have deprecated
+  in favor of more generalized methods that serves the same purposes,
+  matchdata/matchtree and matchdata/matchset.
+- Added module/include_as.
+- Added array/permute.
+
+v0.6.3:
+- Gem is now avaliable!
+- Added kernel/require_all which allows one to require a pattern of files,
+  making it easy to require every file in a directory.
+- Added hash/traverse and hash/traverse!, which takes a block and iterates over
+  each key-value pair descending into subhash values and applying the block.
+  (Thanks goes to Ara T. Howard and robert for their help.)
+- Added hash/collect. This uses enumerable/graph so that
+  hash/collect will return a hash rather then an array.
+- Added numeric/before and numeric/after in place of #ago and #since
+  and aliased #ago and #since to them, per the suggestions of
+  Francis Hwang.
+- Added "poor man's profiler", time/elapse. (Thanks goes to Hal Fulton).
+- Changed enumerable/build_hash to enumerable/graph. The method #build_hash
+  has been aliased to #graph for the time being for backward compatability.
+- Added array/last_index. (Thanks goes to Jabari)
+
+v0.6.2:
+- Added kernel/resc as a shortcut for Regexp.escape.
+- Renamed hash/keys_to_string to hash/key_to_s and  
+  hash/keys_to_symbol to hash/keys_to_sym to be more consistant
+  with other methods and what these methods specifically do.
+  The old names have been deprecated.
+- Added hash/has_keys?, which allows for checking mutliple keys at once.
+  Also includes #has_only_keys?
+- Added Rail's Time and Byte modules for Numeric with
+  numeric/times.rb and numeric/bytes.rb (I've been informed that
+  thanks go to Richard Kilmer for this. Thanks!)
+- Added numeric/octet_unit which utilizes numeric/bytes.
+  (The name of this method may change in the future though.)
+- Added enumerable/uniq_by.
+- Added module/abstract.
+- Added module/redirect which is similar to alias, but does not
+  copy the method, but rather wraps it. It also takes a hash so
+  multiple methods can be redirected all at once.
+- Added string/shatter which is similar to split but includes
+  the matched portions of text.
+  
+v0.6.1:
+- Updated the current set of mix files which were still from 
+  version 0.5.0. (2004-12-31)
+
+v0.6.0:
+- Major revisions made by Florian's onslaught. (2004-12-28) 
+- First general public release.
+
+v0.5.0:
+- This is the beginning of offical releases. (2004-12-23)
+
+v0.1.0:
+- Now called Facets.
+- Changed layout to be completely atomic! (2004-10-30)
+
+v0.0.4:
+- Scoured the Ruby world for useful additions.
+- Changed name again from A.B.C. to Raspberry.
+  I can't seem to settle on a name. Even the new 
+  subsections have changed five times. (2004-08-08)
+
+v0.0.3:
+- Reorganinzed all of this together in a nice neat way.
+- Changed name of library from Succ to A.B.C. 
+  which stands for All Base Common. (2004-02-02)
+    
+v0.0.2:
+- A number of new methods added.
+- Renamed it Succ for "successor". (2003-05-31)
+
+v0.0.1:
+- Tomslib's just a few useful methods. (2002-07-01)

data/README

@@ -0,0 +1,161 @@
+
+= Nano Methods
+
+=== Ruby's Atomic Library
+
+
+== What is Ruby's Atomic Library?
+
+Nano Methods is the a vast collection of general purpose core extension methods
+for the Ruby programming language. It is unique in that it is an _atomic_ library 
+-- the methods are stored individually so that each can be required independently.
+This gives the programmer greater control to include only the extra methods he or
+she actually needs. The package currently contains over 400 methods spanning 27
+classes and modules.
+
+
+== Installation
+
+The easiest way to install is via RubyGems. On the command line enter:
+
+  > gem install nano
+
+To manually install, unpack the .tbz (.tar.bz2) package and use the included setup.rb script.
+For example:
+
+  > tar -xvzf nano-x.y.z.tbz
+  > cd nano--x.y.z
+  > sudo ruby setup.rb
+
+
+== Usage
+
+=== The Nano Methods
+
+There are quite a few methods. For detailed usage of any given method please
+refer to the API RDocs. Most are well documented.
+
+You can start using nano simply by requiring methods. For example:
+
+  require 'nano/time/stamp'
+
+This works fine for all cases EXCEPT when there is punctuation used in the method name.
+Nano has used URI escaped codes in those cases. For example.
+
+  require 'nano/nilclass/empty%3F'
+
+But who really want's to hur their brain so? ;) To remedy, you can first,
+
+  require 'nano/kernel/require_nano'
+
+Now you can require nano-methods without difficulty. The above becomes:
+
+  require_nano 'nilclass/empty?'
+
+The method #require_nano is actually a wrapper around another method #require_esc,
+except that it automatically furnishes the 'nano/' path. You could have instead
+used:
+
+  require_esc 'nano/nilclass/empty?'
+
+The layout of Nano's files is straightfoward and well organized. All individual methods
+are storeed in subdirectories under their effected downcased class' or module's name.
+
+  require 'nano/<class|module>/<method-name>'
+
+Convenient "require-"groupings" are kept under the main path-space 'nano'. 
+The most important among these gorupings is 'nano/base'. This loads all
+the nano methods considered fundamental, ie. the ones so basic that Ruby 
+might have just as well had them built-in --about two dozen methods in all
+(and include require_nano and require_esc). Nano's base methods are common
+enough that a direct shortcut has been provided to them via
+
+  require 'nano'
+
+Another grouping of interest is 'nano/full'. This "require-grouping" requires
+nearly every nano-method there is. The only methods NOT required are those
+considered "cautionary" or "unsafe" in the way they effect Ruby b/c they
+may potentially disrupt pre-existing code. (Such "unsafe" methods are not
+useless however; one just needs to be well aware of their effects and,
+hence, must require them specifically.)
+
+There are also a number of other sets for requiring methods in mass.
+For example to load every nano method related to randomness use:
+
+  require 'nano/randomness'
+
+The alternative way to use Nano, is the new advance "auto-escape" require
+system.
+
+  require 'nanosys'
+
+This puts in place an alternate Kernel#require method, insuring that all
+the methods, will be escaped as needed and loaded correctly. After this you
+can require any nano-method simply by using the normal #require method --no
+need for the special methods.
+
+
+== Contribute
+
+The project thrives on contribution. Please feel free to offer any
+extension you wish. The criteria for inclusion is fairly light:
+
+* Is it generally useful and/or highly interesting? 
+* Can it pass a basic testcase?
+
+If it meets these requirements then there's a fair chance that it will
+be accepted into Nano-Methods. 
+
+
+== Authorship
+
+This collection was put together by, and largely written by Thomas Sawyer
+(aka Trans Onoma). He can be reached via email at transfire at gmail.com.
+
+Some parts of this collection were written and/or inspired by other
+persons. Fortunately nearly all were copyrighted under the same open
+license as this library (Ruby). In the few excpetions I have included the
+copyright notice with the source code. In all cases, I have made every
+effort to give credit where credit is due. You will find these copyrights,
+thanks and acknowledgements embedded in the source code, and a simple
+"Author(s)" section is given in the RDocs.
+
+Authors include:
+
+* Thomas Sawyer
+* George Moschovitis
+* Florian Gross
+* Gavin Sinclair
+* Florian Frank
+* Hal Fulton
+* Renald Buter
+* Paul Brannan
+* Michael Granger
+* Michael Neumann
+* Peter Vanbroekhoven
+* Derek Lewis
+* Thomas-Ivo Heinen
+* Mohammad Khan
+* Jan Molic
+
+If anyone is missing from the above list, please let me know and 
+I will correct right away. Thanks.
+
+
+== License
+
+In so far as it matters, the collection PER COLLECTION is licensed as follows:
+
+Nano Methods
+Copyright (c) 2004,2005 Thomas Sawyer
+Ruby License
+
+The Ruby license is a dual license that also provides for use of the GPL.
+A copy of both licenses accompany this document.
+
+
+== Pitch
+
+ALL YOUR BASE ARE BELONG TO RUBY
+
+