Thanks ... looked OK and seemed to work (not break my existing code)
so I applied it, though I don't have any testcases for what it's
supposed to do.
I've got some that I use for internal testing - but the most obvious is that
you should now be able to read any valid UTF-8 sequence into a
On Wednesday, September 10, 2003, at 11:46 AM, Pete French wrote:
BTW- I dont understand some of the GNUstep architecture that well.
There
are several implementations of rangeOfComposedCharaterSequenecAtIndex
- how do I know which is used when ? I note that one of them appears
not
to use the
The one in NSString.m is used whenever anyone implements their own
subclass of NSString.
O.K., so I can test that by making an empty subclass of NSString then ?
-bat.
___
Bug-gnustep mailing list
[EMAIL PROTECTED]
On Wednesday, September 10, 2003, at 12:34 PM, Pete French wrote:
The one in NSString.m is used whenever anyone implements their own
subclass of NSString.
O.K., so I can test that by making an empty subclass of NSString then ?
Unfortunately not quite that simple ... NSString is the semi-abstract
On Wednesday, September 10, 2003, at 01:01 PM, Pete French wrote:
All the other methods should already be implemented in NSString.m in
terms of those primitives.
Are there any existing subclasses of NSString which use these methods
Not that I know of.
that I could use for testing, or is it best
Hi Pete,
just tired this with your favourit UTF-8 page and I was able to copy it
from Mozilla over to Ink. Great now all that Unicode copying should be
working. (Not that I ever wanted to copy that page anyway)
Cheers
Fred
Richard Frith-Macdonald wrote:
On Tuesday, September 9, 2003, at 10:41
This patch seems to have broken parts of the string handling. When I
tried running the test suite today, it not only failed, it dumped core
during the string tests.
Our test suite isn't complete in any way, but it does cover a lot of
things, and a fair amount of important stuff. I'd like to
On Thursday, September 11, 2003, at 02:09 AM, Alexander Malmberg wrote:
This patch seems to have broken parts of the string handling. When I
tried running the test suite today, it not only failed, it dumped core
during the string tests.
I re-ran the tests and it was fine ... then I checked and
