# Binary Search 0.0.2 released

**URL:** <https://www.ruby-forum.com/t/binary-search-0-0-2-released/118622>\
**Category:** Ruby\
**Created:** [October 29, 2007, 3:47pm UTC](https://www.ruby-forum.com/t/binary-search-0-0-2-released/118622 "2007-10-29T15:47:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![luispulidoman](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/dec6dc/32.png) [@luispulidoman](https://www.ruby-forum.com/u/luispulidoman)\
**Post date:** [October 29, 2007, 3:47pm UTC](https://www.ruby-forum.com/t/binary-search-0-0-2-released/118622/1 "2007-10-29T15:47:58Z")

</div>

Hi

A few weeks after Ruby Q. 139 I found myself needing again to do a  
binary search in a big text file. So I converted the solution  
submitted to OOP and released it as a rubygem.

With this gem, you create first an index of the file you need to  
search and then do the searches. More info at  
[http://binarysearch.rubyforge.org/](http://binarysearch.rubyforge.org/)

Bye,

---

<div class="post-metadata">

**Author:** ![luispulidoman](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/dec6dc/32.png) [@luispulidoman](https://www.ruby-forum.com/u/luispulidoman)\
**Post date:** [October 29, 2007, 4:17pm UTC](https://www.ruby-forum.com/t/binary-search-0-0-2-released/118622/2 "2007-10-29T16:17:13Z")

</div>

Luis P. wrote:

> Bye,

Sorry but I guess the gem’s name is somewhat inadequate. This is not a  
binary search library, but a text indexing and searching library which  
happens to employ a binary search algorithm. So you essentially reserve  
this gem name from some possible real binsearch library…

mortee

---

<div class="post-metadata">

**Author:** ![luispulidoman](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/dec6dc/32.png) [@luispulidoman](https://www.ruby-forum.com/u/luispulidoman)\
**Post date:** [October 29, 2007, 6:16pm UTC](https://www.ruby-forum.com/t/binary-search-0-0-2-released/118622/3 "2007-10-29T18:16:04Z")

</div>

On 10/29/07, mortee [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> Sorry but I guess the gem’s name is somewhat inadequate. This is not a  
> binary search library, but a text indexing and searching library which  
> happens to employ a binary search algorithm. So you essentially reserve  
> this gem name from some possible real binsearch library…

You’re right. I never stop for a second thought about the gem’s name.  
Maybe I choose some cryptic name where there is no chance of  
collision.

---

<div class="post-metadata">

**Author:** ![luispulidoman](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/dec6dc/32.png) [@luispulidoman](https://www.ruby-forum.com/u/luispulidoman)\
**Post date:** [October 29, 2007, 9:52pm UTC](https://www.ruby-forum.com/t/binary-search-0-0-2-released/118622/4 "2007-10-29T21:52:00Z")

</div>

Luis P. wrote:

> On 10/29/07, mortee [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:
> 
> > Sorry but I guess the gem’s name is somewhat inadequate. This is not a  
> > binary search library, but a text indexing and searching library which  
> > happens to employ a binary search algorithm. So you essentially reserve  
> > this gem name from some possible real binsearch library…
> 
> You’re right. I never stop for a second thought about the gem’s name.  
> Maybe I choose some cryptic name where there is no chance of  
> collision.

I haven’t intended to suggest a cryptic name - just something more  
specific to what your gem actually does.

mortee

---

<div class="post-metadata">

**Author:** ![luispulidoman](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/dec6dc/32.png) [@luispulidoman](https://www.ruby-forum.com/u/luispulidoman)\
**Post date:** [October 30, 2007, 4:04pm UTC](https://www.ruby-forum.com/t/binary-search-0-0-2-released/118622/5 "2007-10-30T16:04:40Z")

</div>

On Oct 29, 2007, at 2:48 PM, mortee wrote:

> > You’re right. I never stop for a second thought about the gem’s name.  
> > Maybe I choose some cryptic name where there is no chance of  
> > collision.
> 
> I haven’t intended to suggest a cryptic name - just something more  
> specific to what your gem actually does.

[http://raa.ruby-lang.org/project/ruby-bsearch/](http://raa.ruby-lang.org/project/ruby-bsearch/)

a @ [http://codeforpeople.com/](http://codeforpeople.com/)
