blurrily 0.2.0 → 0.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 2fb2ab9e2c0e96d8a65f2a86ab5ccda4686cec85
-  data.tar.gz: 1cf52f8ba96a911f8e0ba140c87ff2ed50e68aac
+  metadata.gz: 33d31a6d8f0cd49c19cd9ea8df17cd4d32a2f7cd
+  data.tar.gz: ab8546ee590bd9d5e5025a60d9b337f8472ddafd
 SHA512:
-  metadata.gz: f464ef07e4140191d33d14192eb32a5f39c6493b0709bd0bd3316b0e33b52de6b9cf9ed56bd961f3dd4c2d1078633a0be3007431587efb12e4c2f859310dd61f
-  data.tar.gz: 8b81f4c68be6b464f8d4408e458037c1602e6e448f658c6b2b333b5d8f83f8b6ddfa7fe849b244a0e61b11f6937b68a1b3189f9a417b14cdb97f002bb379f960
+  metadata.gz: 1d19b002f2be93f4eada66e8eedcad5c9a9f3a4b3691c5300e2265fedbefb4e039ebf84fa05eee365a012bff4b0e3181acb6adfed69c37f286dbb17da0e46a89
+  data.tar.gz: 902b01256d823b4719f53c974cc0964a76a2f890bf75b907e91e170e910577aaafb7c18b35a7a5393d417ceb04a6e5e9bfea44691219e75fd6d0f6f9721bae9e

data/README.md

@@ -99,7 +99,7 @@ strings).
 This means that case and diacritrics are completely ignored by Blurrily. For
 instance, *Puy-de-Dôme* is strictly equivalent to *puy de dome*.
 
-It also means that any non-latin input will probably result in garbase data
+It also means that any non-latin input will probably result in garbage data
 and garbage results (although it won't crash).
 
 ### Multi-word needles and edge stickyness.
@@ -109,7 +109,7 @@ Multi-word needles (say, *New York*) are supported.
 The engine always favours matches that begin and end similarly to the
 needle, with a bias to the beginning of the strings.
 
-Thsi is because internally, the string *New York* is turned into this
+This is because internally, the string *New York* is turned into this
 sequence of trigrams: `**n`, `*ne`, `new`, `ew*`, `w*y`, `*yo`, `yor`,
 `ork`, `rk*`.
 
@@ -131,7 +131,7 @@ For instance, `/usr/share/dict/words` is a list of 235k English words, and
 weighs 2.5MB. Importing the whole list uses up 75MB of memory, 51MB of which
 are the database.
 
-Note that once a databse has been written to disk and loaded from disk,
+Note that once a database has been written to disk and loaded from disk,
 memory usage is minimal (560KB per database) as the database file is memory
 mapped. For performance you do need as much free memory as the database
 size.

data/ext/blurrily/extconf.rb

@@ -13,7 +13,7 @@ when 'LINUX'
 end
 
 # production
-$CFLAGS += " #{SHARED_FLAGS} -O3 -fno-fast-math"
+$CFLAGS += " #{SHARED_FLAGS} -Os"
 
 # development
 # $CFLAGS += " #{SHARED_FLAGS} -O0 -g"

data/lib/blurrily/version.rb

@@ -1,3 +1,3 @@
 module Blurrily
-  VERSION = "0.2.0"
+  VERSION = "0.2.1"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: blurrily
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.2.1
 platform: ruby
 authors:
 - Julien Letessier
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-04-25 00:00:00.000000000 Z
+date: 2013-05-03 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport