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
Le 09/10/2014 14:14, kilon alios a écrit :
I am almost always right.
Good medicine :)
maybe ask the original author/s via github ? Why do things the hard way ;)
Yes may be I will after having looked closely at the source,
no hard way here, it's not a problem to read c or c++ code,
just a l
Thanks Damien - I’ll load up Nile and see what you guys did. I figured it might
be the case that you have to create a TestTrait - although it does feel a bit
like creating a TestConcreteClass to test an AbstractClass, which also feels a
bit strange - and caused me (probably rightly so), to avoid
Julien,
I recently added bitbucket:// support to metacello[1].
If you follow the installation instructions here[2], you can get the
support loaded into Pharo3.0.
Dale
[1] https://groups.google.com/forum/#!topic/metacello/0vOzvQL10cQ
[2] https://github.com/dalehenrich/metacello-work#pharo30
On
On Thu, Oct 9, 2014 at 2:17 PM, Tim Mackinnon wrote:
> Any thoughts/pointers?
I would tend to create one test trait for each application trait the
same way I create one test class for each application class. That
exactly what I did with the Nile stream trait-based library (there is
a journal pape
I’ve sort of padded around the edges of Traits, and decided to reread the
papers and better understand them.
One thing that occurs to me - if you want to test your traits, is the only
suggested mechanism to test them in-situ with the classes that use them OR can
you poof one up and test it by e
I am almost always right.
maybe ask the original author/s via github ? Why do things the hard way ;)
On Wed, Oct 8, 2014 at 8:54 AM, Alain Rastoul wrote:
> You are both right.
> Question about nanomsg is the thread model (a big bonus of 0mq), which is
> not clear to me.
> they state: "...In nan
