You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Inspect: (Character cr asString, ' abc') trimBlanks
What is the expected output? What do you see instead?
On Squeak and Dolphin, I see 'abc'; on VW and VA Smalltalk I see '
abc' (a CR, three spaces, and 3 letters).
What version of the product are you using? On what operating system?
Seaside-Core pmm.141
Seaside-Squeak-Core lr.44
Seaside-Test pmm.112
Running on WinXP
Please provide any additional information below.
Since the #trimBlanks method actually removes all separators, it seems
badly named at best.
Both VW and VA Smalltalk implement String>>#trimBlanks to remove only
spaces, not all separators. Dolphin's #trimBlanks implementation matches
Seaside-Squeak-Core; I don't know about GST or Gemstone.
VA Smalltalk has a similar method, #trimSeparators, to remove all
separators; I have not found a similar method in other implementations.
I suggest changing the Seaside-Squeak-Core String>>#trimBlanks method (and
references to it) to String>>#trimSeparators to more-correctly describe
its function as well as aiding porting.
Original issue reported on code.google.com by wembley....@gmail.com on 6 May 2008 at 4:06
The text was updated successfully, but these errors were encountered:
… when logging a commit conflict to the object log, we'll just pass the url of the native request ... unless the GsSocket is sneaking into a persistent root some other (less obvious way) ... logging commit conflicts should now be safe and hopefully the FastCGI-related GsSocket "lost state" errors nuked
dalehenrich
pushed a commit
to dalehenrich/Seaside
that referenced
this issue
Sep 7, 2015
Original issue reported on code.google.com by
wembley....@gmail.com
on 6 May 2008 at 4:06The text was updated successfully, but these errors were encountered: