Re: possible change to is_digit, is_wordchar, etc

2005-05-09 Thread Patrick R. Michaud
On Sun, May 08, 2005 at 11:45:08PM +0200, Jens Rieks wrote: > Hi, > > C is now implemented. The second part (find_(not_)cclass) will > follow tomorrow. Wow, yippee -- that is fast! There were several times yesterday when I really wished for find_not_cclass, so this will really clean up (and spe

Re: possible change to is_digit, is_wordchar, etc

2005-05-08 Thread Jens Rieks
Hi, C is now implemented. The second part (find_(not_)cclass) will follow tomorrow. jens PS: The "get_byte past the end of the buffer (1 of 1)" error is hopefully fixed, too. Don't know if it is the cleanest way, but it at least works :-)

Re: possible change to is_digit, is_wordchar, etc

2005-05-07 Thread Jens Rieks
On Saturday 07 May 2005 12:06, Leopold Toetsch wrote: > Patrick R. Michaud wrote: > > I'd like to make a slight change to the is_digit, is_wordchar, > > and other is_* ops. Currently calling these ops at the offset > > following the last codepoint results in a > > "get_byte past the end of the buf

Re: possible change to is_digit, is_wordchar, etc

2005-05-07 Thread Leopold Toetsch
Patrick R. Michaud wrote: I'd like to make a slight change to the is_digit, is_wordchar, and other is_* ops. Currently calling these ops at the offset following the last codepoint results in a "get_byte past the end of the buffer (1 of 1)" error, it would be nicer if they simply returned false (0

possible change to is_digit, is_wordchar, etc

2005-05-07 Thread Patrick R. Michaud
I'd like to make a slight change to the is_digit, is_wordchar, and other is_* ops. Currently calling these ops at the offset following the last codepoint results in a "get_byte past the end of the buffer (1 of 1)" error, it would be nicer if they simply returned false (0) at this one position. (