Yep, you're right. Apparently my checkin also added two tests for concat() to t/op/string.t that the current parrot was not ready to deal with. In any case, it's all better now.
Richard Soderberg wrote: > Did you forget the string.c checkin? Parrot cvs failing, don't see string_ord >anywhere, and cvs logs don't show a string.c update. > > R. > > > -----Original Message----- > > From: Jeff [mailto:[EMAIL PROTECTED]] > > Sent: Monday, November 12, 2001 11:46 PM > > To: [EMAIL PROTECTED] > > Subject: [PATCHES] ord(i,s|sc(,i|ic)?) operator committed, > > fixed bug in > > concat() > > > > > > Documentation updated, and tests added to t/op/string.t. > > The CVS log details most of the changes, but basically: > > > > core.ops - Added ord() opcode > > string.c - Added string_ord() and a _string_index() helper function to > > help making accommodating different encodings easier. Patched concat() > > to deal with null strings. > > t/op/string.t - Added tests for ord() opcode, added a few > > null tests for > > concat(). > > > > At a suggestion from Alex Gough, the three-argument ord opcode now > > behaves like perl's arrays when given negative indices. Read > > the opcode > > documentation for more information. > > > > --Jeff > > <[EMAIL PROTECTED]> > > > > -- --Jeff <[EMAIL PROTECTED]>
