Re: Issue 166 in glassdb: discrepancy between Pharo regex and Gemstone on multiline strings

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Issue 166 in glassdb: discrepancy between Pharo regex and Gemstone on multiline strings

glassdb
Updates:
        Status: Fixed
        Labels: Fixed-1.0-beta.8.5

Comment #6 on issue 166 by [hidden email]: discrepancy between Pharo  
regex and Gemstone on multiline strings
http://code.google.com/p/glassdb/issues/detail?id=166

Ported the absolute latest Regex code from Pharo to GemStone.

Name: Regex-Core-DaleHenrichs.3
Author: DaleHenrichs
Time: 12/08/2010, 17:11:45
UUID: b7a9bcf5-8016-42f9-8dd9-d0b05d02274b
Ancestors: Regex-Core-StephaneDucasse.2

Name: Regex-Tests-Core-DaleHenrichs.3
Author: DaleHenrichs
Time: 12/08/2010, 17:15:39
UUID: 9b64e9d4-7674-4de1-930f-a5b1cebd3179
Ancestors: Regex-Tests-Core-StephaneDucasse.2

At the moment these packages have been committed to GemSource due to a  
couple of minor problems that prevented me from using the Pharo versions of  
the packages directly:

- moved RxMatcher>>split: to GsPharo since it calls #assertWithDescription:  
which is Pharo-specific (along with #splitOn: being implemented in GsPharo,  
too). If call #assertWithDescription: is removed, then the Pharo packages  
can be used unchanged in GemStone (Pharo Issue 3391  
http://code.google.com/p/pharo/issues/detail?id=3391 submitted).
Name: GsPharo-Core-DaleHenrichs.5
Author: DaleHenrichs
Time: 12/08/2010, 17:26:01
UUID: 820b9d12-45b9-472e-9dcd-d154cf6d4bd6
Ancestors: GsPharo-Core-DaleHenrichs.4

Name: GsPharo-Tests-DaleHenrichs.5
Author: DaleHenrichs
Time: 12/08/2010, 17:26:24
UUID: e8627b9a-a56a-41ab-b401-4ac5410b6b79
Ancestors: GsPharo-Tests-DaleHenrichs.4

- two methods in Regex-Tests-Core had doubled $. which cause GemStone  
compile errors. If those two methods are fixed then the Pharo packages can  
be used directly in GemStone



Reply | Threaded
Open this post in threaded view
|

Re: Issue 166 in glassdb: discrepancy between Pharo regex and Gemstone on multiline strings

glassdb

Comment #7 on issue 166 by [hidden email]: discrepancy between Pharo  
regex and Gemstone on multiline strings
http://code.google.com/p/glassdb/issues/detail?id=166

woops forgot support code in:

Name: Squeak-DaleHenrichs.251
Author: DaleHenrichs
Time: 12/08/2010, 17:31:59
UUID: 17e67b90-ac0c-4f78-a6cb-76764f4cf1f4
Ancestors: Squeak-DaleHenrichs.250


Reply | Threaded
Open this post in threaded view
|

Re: Issue 166 in glassdb: discrepancy between Pharo regex and Gemstone on multiline strings

glassdb

Comment #8 on issue 166 by [hidden email]: discrepancy between Pharo  
regex and Gemstone on multiline strings
http://code.google.com/p/glassdb/issues/detail?id=166

Missed this package too:

Name: GemStone-ANSI-Streams-DaleHenrichs.1
Author: DaleHenrichs
Time: 12/08/2010, 17:32:03
UUID: f5eb4ec6-d2a0-418e-8bdf-648cfc8dc6d0
Ancestors:

In this case, AnsiReadStream, AnsiWriteStream, and AnsiReadWriteStream have  
been moved from Grease (GemStone) to the core, since they are expected to  
be useful in General whether or not Grease is loaded ... when using stream  
based Regex for example it is recommended that you use Ansi* streams for  
correct behavior ... SequenceableCollection #readStream and #writeStream  
now use the Ansi* streams so it shouldn't be too hard to ensure that you  
use them ...