On Mon, May 11, 2015, at 12:27 PM, Paul DeBruicker wrote:
> If you've gotta have prorobuf then you've gotta have protobuf but there
> is a
> thrift implementation (https://thrift.apache.org/) and also a message
> pack
> implementation (https://code.google.com/p/stomp-serializer/)
>
There are unfo
Hey all,
Has anyone implemented protobufs for Pharo yet? I’ve not managed to find any
examples, so I assume the answer is “no”, but I thought I’d check here before
rolling up my sleeves and writing one myself. (My specific target here is to
write a RethinkDB driver, so if someone has magically
On Sun, 05 Oct 2014 16:51:25 -0400, Sven Van Caekenberghe
wrote:
[snip]
Apart from that, the tokenisation is not very efficient, #lines is a
copy of your whole contents, so is the #split: and #trimmed. The
algorithm sounds a bit lazy as well, writing it 'on purpose' with an eye
for perfor
On Sun, 05 Oct 2014 16:51:25 -0400, Sven Van Caekenberghe
wrote:
Working with WideStrings is way slower than working with ByteStrings,
there is just no way around that. What is especially slow is the
automagic switch from ByteString to WideString, for example in a
String>>#streamContents
On Sun, 05 Oct 2014 10:36:31 -0400, Sven Van Caekenberghe
wrote:
How come you got WideStrings ?
What does the input look like, can you give a partial example ?
I'm guessing I got WideStrings because the file is indeed in UTF-8, with
lots of characters outside the lower 128 code points. A
On Fri, 03 Oct 2014 16:13:35 -0400, stepharo wrote:
Looking at MessageTally, it seems at least half of that 278ms is spent
noodling around in WideStrings and other small things that the Spur
object format ought to help with, so it'd be interesting to see how much
of a speed boost that gives with
My apologies if this is already spelled out somewhere and I simply can't
find it, but are there any Spur images for Pharo yet? I can only find
Squeak ones. It's not a big deal either way; I was just playing with an
algorithm that, after very heavy optimization, I was able to get down to
about 278
On Wed, 24 Sep 2014 13:03:57 -0400, Sven Van Caekenberghe
wrote:
Did you read the actual conversation in the issue ?
https://pharo.fogbugz.com/f/cases/14054/Issue-with-path-with-accented-characters
It has been renamed and there is a fix (as a change set, not as a slice,
yet). Basically
On Mon, 22 Sep 2014 17:58:41 -0400, Sven Van Caekenberghe
wrote:
I also find the way some problems are reported quite disturbing. How
much testing did you do ? On which platforms ?
I can do this (in Pharo 3) without any problems (we're talking about
arbitrary Unicode characters in path n
On Tue, 23 Sep 2014 08:51:54 -0400, Hilaire wrote:
Le 23/09/2014 14:09, Damien Cassou a écrit :
I recently read documents about utf-8 encoding. In all of them, the
author says that pathnames should be kept as is because you never know
which encoding the filesystem uses. So, a filename should p
10 matches
Mail list logo
