Issue 216 in glassdb: stream upToAll leaves stream position in a different place than in Pharo.

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

Issue 216 in glassdb: stream upToAll leaves stream position in a different place than in Pharo.

glassdb
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium GLASS-Server Version-GLASS0.231

New issue 216 by [hidden email]: stream upToAll leaves stream position  
in a different place than in Pharo.
http://code.google.com/p/glassdb/issues/detail?id=216

In Pharo:
     'http://vimeo.com/18375790' readStream upToAll: '.com/'; upToEnd.
results in:
     '18375790'

In Gemstone the same code results in:
     '.com/18375790'

This is caused by the stream position after #upToAll: . In Pharo the  
following:
     'http://vimeo.com/18375790' readStream upToAll: '.com/'; position
results in:
      17

In Gemstone the same code results in:  12

Reply | Threaded
Open this post in threaded view
|

Re: Issue 216 in glassdb: stream upToAll leaves stream position in a different place than in Pharo.

glassdb
Updates:
        Status: Accepted
        Owner: [hidden email]
        Labels: Milestone-1.0-beta.8.6

Comment #1 on issue 216 by [hidden email]: stream upToAll leaves stream  
position in a different place than in Pharo.
http://code.google.com/p/glassdb/issues/detail?id=216

(No comment was entered for this change.)

Reply | Threaded
Open this post in threaded view
|

Re: Issue 216 in glassdb: stream upToAll leaves stream position in a different place than in Pharo.

glassdb
Updates:
        Labels: -Milestone-1.0-beta.8.6 Milestone-1.0-beta.9

Comment #2 on issue 216 by [hidden email]: stream upToAll leaves stream  
position in a different place than in Pharo.
http://code.google.com/p/glassdb/issues/detail?id=216

Nick,

#upToAll: is one of those selectors with different behavior on different  
platforms. There's #greaseUpToAll: that should be used to get common  
behavior across platforms ...

In looking at senders I could probably get away with overriding the  
GemStone #upToAll:...

So if you think #greaseUpToAll: would be too cheesy, let me know and I'll  
take a crack at the override ... until then, I'll defer making a change  
until after 1.0-beta.8.6

Reply | Threaded
Open this post in threaded view
|

Re: Issue 216 in glassdb: stream upToAll leaves stream position in a different place than in Pharo.

glassdb

Comment #3 on issue 216 by [hidden email]: stream upToAll leaves  
stream position in a different place than in Pharo.
http://code.google.com/p/glassdb/issues/detail?id=216

I wasn't aware of #greaseUpToAll: I'll switch to using that. Thanks

Reply | Threaded
Open this post in threaded view
|

Re: Issue 216 in glassdb: stream upToAll leaves stream position in a different place than in Pharo.

glassdb
Updates:
        Status: Fixed

Comment #4 on issue 216 by [hidden email]: stream upToAll leaves stream  
position in a different place than in Pharo.
http://code.google.com/p/glassdb/issues/detail?id=216

greaseUpToAll: is okay to use...