On Mon, Jul 23, 2018 at 07:38:16PM +0100, Denis Kudriashov wrote:
> Hi.
>
> I wonder does not stdout and stdin are always about text input/output?
No. Consider the case of reading and writing serialized objects on stdin
and stdout, possibly between two images sending serialized objects to one
ano
On 24 July 2018 at 02:38, Denis Kudriashov wrote:
>
> 2018-07-23 19:19 GMT+01:00 Alistair Grant :
>>
>> Hi Pavel & Sven,
>>
>> Thanks for writing this, it is a great quick reference.
>>
>>
>> On Mon, 23 Jul 2018 at 12:08, Sven Van Caekenberghe wrote:
>> >
>> >
>> >
>> > > On 23 Jul 2018, at 11:13
Hi Norbert,
I'm glad you're doing this. You might post this announcement to the
Cryptography list:
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/cryptography
& Squeak Dev.
And Dale Henrich did a port to GemStone here:
https://github.com/gsdevkit/cryptography
But I'm not sure if
Hi.
I wonder does not stdout and stdin are always about text input/output?
I never saw examples when somebody explicitly write raw bytes into these
streams.
If I am right then it is better to introduce binaryStdout and binaryStdin
messages. And make stdout and stdin use most common encoding by de
Hi Pavel & Sven,
Thanks for writing this, it is a great quick reference.
On Mon, 23 Jul 2018 at 12:08, Sven Van Caekenberghe wrote:
>
>
>
> > On 23 Jul 2018, at 11:13, Ben Coman wrote:
> >
> > I like all the new code examples until "Write a UTF-8 text to STDOUT"
> > and I wonder "Stdio stdout
Hi Richard,
Thanks for pointing out the difference between #on: and #with: instance
creation methods.
This lead me to discover that ReadWriteStream>>on: strangely sets the readLimit
instvar to the end… which is not what I would expect.
Removing that method and reversing the change in the commit
> On 23 Jul 2018, at 18:52, Richard O'Keefe wrote:
>
> Oh, I think a clarification is needed when talking about UTF-8.
Why ?
> To the best of my knowledge you don't need a Byte-Order-Mark at
> the beginning of a UTF-8 stream because there is no byte order
> issue to result,
Nothing was said
Great!!
On Mon, Jul 23, 2018, 09:00 Norbert Hartl wrote:
> After several attempts to solve the Cryptography package problems over the
> years I decided to move it on my own to github.
>
> What I did:
>
> - researched all authors and used the git migration tool to get the
> package from smalltalk
I am a little confused by Filestreams.MD
#position and #position: report and set the number of past items.
So when you open a stream, #position is 0. So why does the first
"Positionable streams" example use ... position: 4 ... while the
second one skips 3 characters? ... position: 3 ... would be
Andrew Black-2 wrote
>> spec
>> baseline: 'SmaCC' with: [ spec loads: #('Reification' )
>> ]
>
> Can you tell me what this line actually means. That is, what does the
> #baseline:with: method actually declare?
It means load the 'Reification' group of the SmaCC
(ReadWriteStream on: 'abc') contents
==> 'abc' in GNU Smalltalk and Dolphin
==> '' in Squeak 6.0 and ST/X
Here I think we see why ANSI Smalltalk defined #with:
for {Read,}WriteStreams but not #on:.
When you recall that ReadWriteStream is a subclass of
WriteStream in most Smalltalks, and that
(Wri
Esteban A. Maringolo wrote
> Good work Norbert. Thanks!
+1
-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
Good work Norbert. Thanks!
Esteban A. Maringolo
El lun., 23 jul. 2018 a las 8:59, Norbert Hartl () escribió:
>
> After several attempts to solve the Cryptography package problems over the
> years I decided to move it on my own to github.
>
> What I did:
>
> - researched all authors and used th
After several attempts to solve the Cryptography package problems over the
years I decided to move it on my own to github.
What I did:
- researched all authors and used the git migration tool to get the package
from smalltalkhub to github
- released a version 0.1 that should be exactly the sam
> On 23 Jul 2018, at 09:38, Pavel Krivanek wrote:
>
> Hello,
>
> I've prepared a draft of a short document that should help you with the
> transition to the "new" file streams API in Pharo 7.
>
> https://github.com/pavel-krivanek/pharoMaterials/blob/master/Filestreams.MD
>
> Pull requests
> On 23 Jul 2018, at 11:13, Ben Coman wrote:
>
> On 23 July 2018 at 15:38, Pavel Krivanek wrote:
>> Hello,
>>
>> I've prepared a draft of a short document that should help you with the
>> transition to the "new" file streams API in Pharo 7.
>>
>> https://github.com/pavel-krivanek/pharoMater
Hi,
As I’m diving into the changes and why it fails:
(ReadWriteStream on: ‘abc’) contents
-> = ‘abc’ on Pharo 6
-> = ‘’ on Pharo 7
That seems wrong to me.
(I’ve also sent this question via github on the commit itself
https://github.com/pharo-project/pharo/commit/9e442addff3790af0c78dbc73f1f349
On 23 July 2018 at 15:38, Pavel Krivanek wrote:
> Hello,
>
> I've prepared a draft of a short document that should help you with the
> transition to the "new" file streams API in Pharo 7.
>
> https://github.com/pavel-krivanek/pharoMaterials/blob/master/Filestreams.MD
>
> Pull requests are welcome.
Hello,
I've prepared a draft of a short document that should help you with the
transition to the "new" file streams API in Pharo 7.
https://github.com/pavel-krivanek/pharoMaterials/blob/master/Filestreams.MD
Pull requests are welcome.
Cheers,
-- Pavel
19 matches
Mail list logo
