On Apr 10, 2004, at 6:13 AM, Leopold Toetsch wrote:
2) String PBC layout. The internal string type has changed. This currently breaks native_pbc tests (that have strings) as well as some "parrot xx.pbc" tests related to strings.
These are working for me (which tests are failing for you?)--I did update the PF_* API to match the changes to string internals. Of course, since the internals changed the pbc layout changed also, so the native_pbc test files need to be regenerated on the various platforms--but the ppc one I submitted (see other post, or original patch submission) should work. But if that one fails for you, it's probably b/c of byte order, and I need to look and find where we do the endianness correction for integers in pbc files, and hook in to do something similar for certain string cases.
Here's a patch to src/pf_items.c, and a ppc t/native_pbc/number_3.pbc. If it's working correctly, the attached strings-and-byte-order.* should both do the same thing--output the Angstrom symbol. If it's wrong, then the pbc version should output junk on a little-endian system.
(If your terminal emulator isn't prepared to handle UTF-8, then pipe the output through 'less', and you should see something like "<E2><84><AB>".)
(PS--I had to give the pbc file a fake extension, to keep the develooper mail server from rejecting it.)
JEff
pf_items_c.patch
Description: Binary data
number_3.pbc
Description: Binary data
strings-and-byte-order.pasm
Description: Binary data
strings-and-byte-order.pbc.file
Description: Binary data
