shared-text substrings, start/end indices, xs><, etc.
shivers@xxxxxx
(25 Jan 2000 01:02 UTC)
|
Re: shared-text substrings, start/end indices, xs><, etc.
sperber@xxxxxx
(25 Jan 2000 07:47 UTC)
|
shared-text substrings
shivers@xxxxxx
(25 Jan 2000 16:06 UTC)
|
Re: shared-text substrings
sperber@xxxxxx
(25 Jan 2000 16:54 UTC)
|
Re: shared-text substrings
shivers@xxxxxx
(25 Jan 2000 17:15 UTC)
|
Re: shared-text substrings sperber@xxxxxx (25 Jan 2000 17:54 UTC)
|
Re: shared-text substrings
shivers@xxxxxx
(25 Jan 2000 19:18 UTC)
|
Re: shared-text substrings
sperber@xxxxxx
(26 Jan 2000 07:30 UTC)
|
Re: shared-text substrings, start/end indices, xs><, etc.
d96-mst-ingen-reklam@xxxxxx
(28 Jan 2000 12:41 UTC)
|
Re: shared-text substrings sperber@xxxxxx 25 Jan 2000 17:54 UTC
>>>>> "Olin" == shivers <xxxxxx@ai.mit.edu> writes: Olin> But I may be *wrong* seeing an opportunity for optimization where in Olin> fact there is none. Olin> Hey, I just provide the functionality. It's up to the programmers to Olin> misuse it well. I just doubt it's worth the tradeoff. Is there hard data that the optimizations you envision actually give significant performance gains? I've always found non-shared strings plenty fast. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla