# Textpow 0.9.0 Released

**URL:** <https://www.ruby-forum.com/t/textpow-0-9-0-released/103989>\
**Category:** Ruby\
**Created:** [May 12, 2007, 1:28pm UTC](https://www.ruby-forum.com/t/textpow-0-9-0-released/103989 "2007-05-12T13:28:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dizan\_V](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/eada6e/32.png) [@Dizan\_V](https://www.ruby-forum.com/u/Dizan_V)\
**Post date:** [May 12, 2007, 1:28pm UTC](https://www.ruby-forum.com/t/textpow-0-9-0-released/103989/1 "2007-05-12T13:28:25Z")

</div>

I have the pleasure to announce the first public release (v 0.9.0 ) of  
Textpow

[http://textpow.rubyforge.org](http://textpow.rubyforge.org)

Textpow is a Ruby library to parse TextMate[[http://macromates.com/](http://macromates.com/)]  
bundles.  
Currently, Textpow fully parse Textmate Syntax files (tmSyntax,  
tmLanguage,  
etc).

Dizan V.

---

<div class="post-metadata">

**Author:** ![Dizan\_V](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/eada6e/32.png) [@Dizan\_V](https://www.ruby-forum.com/u/Dizan_V)\
**Post date:** [May 12, 2007, 3:07pm UTC](https://www.ruby-forum.com/t/textpow-0-9-0-released/103989/2 "2007-05-12T15:07:35Z")

</div>

Just a note, textpow requires oniguruma, which currently doesn’t seem  
to run on 64bit machines.

^ manveru

---

<div class="post-metadata">

**Author:** ![Dizan\_V](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/eada6e/32.png) [@Dizan\_V](https://www.ruby-forum.com/u/Dizan_V)\
**Post date:** [May 12, 2007, 3:41pm UTC](https://www.ruby-forum.com/t/textpow-0-9-0-released/103989/3 "2007-05-12T15:41:39Z")

</div>

Yes, there is, indeed, a bug report, about oniguruma (which I  
administer)  
crashing in 64 bit machines. Unfortunately, since I do not have access  
to a  
64 bit computer, I have not been able to verify the problem. At the same  
time, the report is quite old (I believe it was issued for version 0.9.0  
or  
so) and the code base has changed a lot since then.

Could anybody confirm that the problem is still happening? If that is  
the  
case, a detailed description of the error in the project’s tracker will  
be  
welcome. If everything is o.k. now I will close the report.

Thanks,

Dizan
