Sockets should accept integers/bytearrays as well as characters/strings
By Paolo Bonzini - Posted on February 6th, 2008
| Project: | GNU Smalltalk |
| Component: | Bindings: Sockets |
| Category: | task |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | postponed |
Description
This is probably easiest to do with a new class shape, which can also be used for FileStreams. The new shape would accept bytes *and* characters for #at:put:, and return characters always (for backwards compatibility).
Currently, I am working around it in Sport, but it's bad for performance.
Updates
#1 submitted by Paolo Bonzini on Thu, 02/07/2008 - 08:01
| Priority: | normal | » minor |
| Status: | active | » postponed |
Turns out it's not necessary for Sport, lowering priority.