pyper 2.0.0 → 2.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 2f43de20a0dc3027e2e901c3c95d10e362aa4206
-  data.tar.gz: c65128a10ef09ee9c6d04c00eab1e67892f0636a
+  metadata.gz: 81b06431cb27f355d7665ea205cc7a6eafbab5a5
+  data.tar.gz: 7f1d6336b52d4f46b5014a1511ac934a1f6b64de
 SHA512:
-  metadata.gz: 0ae7997b73af3aca89dd773967a44eda8ce37da2234bf89763b7caaa633f956cac3046220cc1da9d697a52b4058ada4a028265d5d628c5d4ccd590fbbaafce31
-  data.tar.gz: bd2147d3a6d3735365da8d6f93b22ec55d7607595e2b617f3ce173a57641125abec8c6a623ba1948fe03b16409d20bad7939f9d3d605b982477e4bf0c88b7580
+  metadata.gz: ba7846834b085f39251741f3d0398e0c65c778294b286fc8e937065dc33b04bcbd80f767efe86325accadef000fe527929c71ac1d10c06639485bad77e2d967c
+  data.tar.gz: 595db729e3fe019c39c2f136e3963d1d9d893d3868cd490c052beebedb9699865c98e19ffa1d3a11f16804c9278edea9201be86b418e98f181a60e3d7699c897

data/README.md

@@ -2,29 +2,18 @@
 
 Pyper is a wide extension of the Lispy car/cdr idea.
 
-## Installation
-
-Add this line to your application's Gemfile:
-
-    gem 'pyper'
-
-And then execute:
-
-    $ bundle
-
-Or install it yourself as:
-
-    $ gem install pyper
-
 ## Usage
 
-Everybody knows Lispy functions #car, #cdr, #caar, #cdar, #cadr, #cddr...
-When you `require 'pyper'` and `include Pyper`, you can try them by yourself:
+Everybody knows Lispy functions `#car`, `#cdr`, `#caar`, `#cdar`, `#cadr`, `#cddr`...
+With Pyper, you have them at the hand:
+```ruby
+require 'pyper'
 
 [1, 2, 3].car # will return the first element, 1
 [1, 2, 3].cdr # will return the remaining elements, [2, 3]
+```
 
-Similarly, #caar will return the first element of the first element, #cadr
+Similarly, `#caar` will return the first element of the first element, `#cadr`
 will return the first element of the remaining elements (that is, second
 element), #cddr will return the list of [3rd, 4th, ... ] elements, etc.
 
@@ -36,34 +25,31 @@ caaaaar, ..., cadaadr, ...
 
 In effect, such character sequences form an APL-like language consisting of
 one-character operators 'a' and 'd', whose combination determines the overall
-operation. Pyper adds a few modifications and widely extends the idea:
+operation. Pyper adds a few modifications and extends the idea:
 
 1. Twin-barrel piping: Instead of just one pipeline, in which the
 operations are applied in sequence, Pyper has 2 parallel pipelines.
 
 2. Greek letters τ, π, χ as method delimiters: Instead of 'c' and 'r' of
 car/cdr family, Pyper methods start and end with any of the characters
-'τ', 'π', 'χ' (small Greek tau, pi and chi). Choice of the character
-conveys specific meaning, which is best explained by case enumeration:
-
-τ...τ means single-pipe input and output,
-τ...π means single-pipe input, double-pipe output
-τ...χ means single-pipe input, double-pipe output with a swap
-π...τ means double-pipe input, single-pipe output
-. . .
-χ...χ means double-pipe input with a swap, and same for the output
-
-(Mnemonic for this is, that τ has one (vertical) pipe, π has two pipes,
-and χ looks like two pipes crossed)
-
-As for the meaning, single-pipe input means, that a single object (the
-message receiver) is fed to the pipeline. Double-pipe input means, that
-the receiver is assumed to respond to methods #size and #[], its size is
-2, and this being fulfilled, pipeline 0 and 1 are initialized
-respectively with the first and second element of the receiver as per
-method #[]. Double-pipe input with swap is the same, but the two
-elements of the receiver are swapped: pipeline 1 receives the first,
-pipeline 0 the second.
+`τ`, `π`, `χ` (_tau_, _pi_ and _chi_). Their meaning is best explained by
+examples:
+
+* `τ...τ` means single-pipe input and output,
+* `τ...π` means single-pipe input, double-pipe output
+* `τ...χ` means single-pipe input, double-pipe output with a swap
+* `π...τ` means double-pipe input, single-pipe output
+* . . .
+* `χ...χ` means double-pipe input with a swap, and same for the output
+
+Mnemonic for this is, that τ looks like a gutter (has one vertical pipe),
+π looks like a twin gutter (two pipes) and χ looks like two pipes crossed.
+Single-pipe input means, that a single object (the receiver) is fed to the
+pipeline 0, while pipeline 1 receives its copy. Double-pipe input means,
+that the receiver should respond to #size and #[], and its size should be 2.
+Pipelines 0 and 1 are then initialized respectively with the first and
+the second element (obtained by #[]). Double-pipe input with swap is the
+same, but the two elements are swapped.
 
 3. Postfix order of commands: While traditional car/cdr family of
 methods applies the letters in the prefix order (from right to left),
@@ -78,27 +64,31 @@ and 'd', is greatly extended.
 
 For example, apart from 'a', mening first, 'b' means second, and 'c'
 means third:
-
+```ruby
 ["See", "you", "later", "alligator"].τaτ    #=>    "See"
 ["See", "you", "later", "alligator"].τbτ    #=>    "you"
 ["See", "you", "later", "alligator"].τcτ    #=>    "later"
+```
 
 For another example, apart from 'd', meaning all except first, 'e' means
 all except first two, and 'f' means all except first three:
-["See", "you", "later", "alligator"].τdτ = ["you", "later", "alligator"]
-["See", "you", "later", "alligator"].τeτ = ["later", "alligator"]
-["See", "you", "later", "alligator"].τfτ = ["alligator"]
+```ruby
+["See", "you", "later", "alligator"].τdτ #=> ["you", "later", "alligator"]
+["See", "you", "later", "alligator"].τeτ #=> ["later", "alligator"]
+["See", "you", "later", "alligator"].τfτ #=> ["alligator"]
+```
 
 These command characters can be combined just like 'a' and 'd' letters
 in the traditional car/cdr family - just beware of the Pyper's postfix
 order:
-
-["See", "you", "later", "alligator"].τddτ = ["later", "alligator"]
-["See", "you", "later", "alligator"].τdeτ = ["alligator"]
-["See", "you", "later", "alligator"].τdeaτ = "alligator"
-["See", "you", "later", "alligator"].τdeadτ = "lligator"
-["See", "you", "later", "alligator"].τdeafτ = "igator"
-["See", "you", "later", "alligator"].τdeafbτ = "g"
+```ruby
+["See", "you", "later", "alligator"].τddτ #=> ["later", "alligator"]
+["See", "you", "later", "alligator"].τdeτ #=> ["alligator"]
+["See", "you", "later", "alligator"].τdeaτ #=> "alligator"
+["See", "you", "later", "alligator"].τdeadτ #=> "lligator"
+["See", "you", "later", "alligator"].τdeafτ #=> "igator"
+["See", "you", "later", "alligator"].τdeafbτ #=> "g"
+```
 
 Allready with these few command characters (a-c, d-f, u-w, x-z, plus
 numbers 0-4 and 5-9), one can compose intelligent car/cdr-like methods.
@@ -116,14 +106,5 @@ as their arity requires.
 
 So much for the main concepts. As for the character meanings, those are
 defined as PostfixMachine methods of the same name (the name consists of
-1 or 2 characters). At the moment, it is necessary to read the
-PostfixMachine code as their documentation.
-
-
-## Contributing
-
-1. Fork it
-2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Commit your changes (`git commit -am 'Added some feature'`)
-4. Push to the branch (`git push origin my-new-feature`)
-5. Create new Pull Request
+1 or 2 characters). At the moment, it is necessary to read the code for
+their documentation.

data/lib/pyper/default_includes.rb

@@ -20,6 +20,12 @@ module Enumerable
   include Pyper
 end
 
+# Pyper is by default included in Enumerable.
+# 
+class Enumerator
+  include Pyper
+end
+
 # Pyper is by default included in Array.
 # 
 class Array

data/lib/pyper/version.rb

@@ -1,4 +1,4 @@
 module Pyper
-  VERSION = "2.0.0"
+  VERSION = "2.0.1"
   DEBUG = 0 # debug level
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: pyper
 version: !ruby/object:Gem::Version
-  version: 2.0.0
+  version: 2.0.1
 platform: ruby
 authors:
 - boris
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-07-21 00:00:00.000000000 Z
+date: 2013-10-26 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: shoulda