i WASN'T suggesting this! Although I feel that you WANT to
be pushed on this one! I was merely suggesting that I (we?
the wider community?) should try and track down these
unaligned traps a little further. If xtl reads lyxstring
incorrectly but is ok with STL string, then you're in a
better position to make a decision about lyxstring's demise.
If, however, it screws up with STL string, then
it's xtl that should be fixed first.
First step, then, is to check and to do that we need to get
the rae branch running with STL string on an Alpha. I have
access to a machine here running AlphaLinux (gcc 2.95.2),
so I can do that now. It would also be useful to get the
rae branch running on a 32 bit machine both with
lyxstring and with STL string. Do we still get these
unaligned access errors or no? If Allan is running on such
a machine, then he can already answer these questions.
Angus
ps. Nice phrase. Is it the same as "Grasp the iron whilst it's hot"?
A.
On Thu, 30 Mar 2000, you wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
>
> | This may of course be a function of my using lyxstring
> | rather than STL string? How much would I need to hack the
> | code base to remove those calls to string::clear() I wonder?
>
> I think we have to "bite i det sure eplet"� and ditch lyxstring, it
> has served us well and it was fun to implement. std::string::clear ==
> std::string::erase(), so q tags-query-replace on all the code should
> be enough to fix that one. A harder problem is that on some
> implementations of std::sting (egcs's) the arguments to
> std::string::replace is in the wrong order so this need to be verified
> and investigated.
>
>
> � (my keyboard does not have a ^1)
> This is a norwegian expression, but I excpet the danes and the
> swedes have the same one: tranlated it means something like "take a
> bite of the sour apple".
