> On 10 Apr 2019, at 15:19, Esteban Maringolo wrote:
>
> I love this attitude coming from the very core of the Pharo dev-team,
> which felt to me as being blind to what other dialects were doing or
> did in the past, and these is days seems to be catching up quite
> quickly.
this was never
Thanks a lot for actually diving into this, this mysterious issue has been
bugging us for a very long time. I do hope you can finally solve this. I am
sure many people will be grateful.
Sven
> On 10 Apr 2019, at 15:38, teso...@gmail.com wrote:
>
> Hello,
>
> After checking the problem with
teso...@gmail.com
wrote:
> If somebody is willing to use it in Pharo 7, I can create a PR against
> Pharo7 to generate patched P7 images.
Yes, I want to
Stephan
Thanks Nicolas.
You know that I appreciate your work.
I would appreciate that Eliot does not send me personal emails to tell that I’m
a bad leader :)
but at least this is coherent with the violent emails I received in the past -
nothing new under the sun.
Just anger against me. I cannot do
Ohhh, my fault, it is trying to look up for the commit of the merge.
That will never work... Because the commit is only in the CI.
On Wed, Apr 10, 2019 at 4:16 PM ducasse wrote:
>
> Pablo I tried the file you sent and I imported it in the PharoLauncher and I
> could not handle file.
> I got a
We need a new stable vm...
On Wed, Apr 10, 2019 at 4:16 PM ducasse wrote:
> Pablo I tried the file you sent and I imported it in the PharoLauncher and
> I could not handle file.
> I got a File class bad argument and after I could not use iceberg.
>
> Stef
>
> > On 10 Apr 2019, at 15:38,
Pablo I tried the file you sent and I imported it in the PharoLauncher and I
could not handle file.
I got a File class bad argument and after I could not use iceberg.
Stef
> On 10 Apr 2019, at 15:38, teso...@gmail.com wrote:
>
> Hello,
>
> After checking the problem with Guille, we have the
Thank you P and G.
It is so annoying.
Stef
> On 10 Apr 2019, at 15:38, teso...@gmail.com wrote:
>
> Hello,
>
> After checking the problem with Guille, we have the hypothesis of the
> source of the problem.
> We have seen that accessing Free Type is not thread-safe.
> Basically, the FTFace
Good find!
The fac tthat FT_Face is not thread-safe is documented
https://www.freetype.org/freetype2/docs/reference/ft2-base_interface.html
Le mer. 10 avr. 2019 à 15:39, teso...@gmail.com a
écrit :
> Hello,
>
> After checking the problem with Guille, we have the hypothesis of the
> source of
Hello,
After checking the problem with Guille, we have the hypothesis of the
source of the problem.
We have seen that accessing Free Type is not thread-safe.
Basically, the FTFace holds a structure that is filled up with the
glyph and its information. As this structure is part of the Font Face
(a
I love this attitude coming from the very core of the Pharo dev-team,
which felt to me as being blind to what other dialects were doing or
did in the past, and these is days seems to be catching up quite
quickly.
Dolphin Smalltalk:
Practically all "widgets" (aka "views") are the native ones, and
Thanks I did not know it was on a mailing-list.
> On 10 Apr 2019, at 14:02, Nicolas Cellier
> wrote:
>
> Hi Stephane,
> If you google 'vm-dev VMMaker.oscog-sk.2367'
> and click one of the first hits
> https://marc.info/?l=squeak-vm-dev=152413936110744=2
>
> On 10 Apr 2019, at 14:01, Cyril Ferlicot wrote:
>
> On Wed, Apr 10, 2019 at 1:52 PM ducasse wrote:
>>
>> Nicolas
>>
>> I tried to find the new primitive and I did not find it here
>>
>>
Hi Stephane,
If you google 'vm-dev VMMaker.oscog-sk.2367'
and click one of the first hits
https://marc.info/?l=squeak-vm-dev=152413936110744=2
you'll see the changes from Sophie:
The new InterpreterPrimitives>>primitiveCompareWith should be linked to
primitive 158.
(and only for ByteString
On Wed, Apr 10, 2019 at 1:52 PM ducasse wrote:
>
> Nicolas
>
> I tried to find the new primitive and I did not find it here
>
> https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/src/plugins/MiscPrimitivePlugin/MiscPrimitivePlugin.c
>
> I found the old one.
> Did I look in the wrong
Nicolas
I tried to find the new primitive and I did not find it here
https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/src/plugins/MiscPrimitivePlugin/MiscPrimitivePlugin.c
I found the old one.
Did I look in the wrong place?
Stef
> On 10 Apr 2019, at 13:46, ducasse wrote:
>
>
Thanks nicolas so we can use them then.
> On 10 Apr 2019, at 11:59, Nicolas Cellier
> wrote:
>
> VMMaker.oscog-sk.2367
> Author: sk
> Time: 19 April 2018, 12:02:35.661622 pm
> UUID: 0c2401e3-1450-4f73-8e81-958f50171595
> Ancestors: VMMaker.oscog- nice.2366
>
> ** new primitive to compare
VMMaker.oscog-sk.2367
Author: sk
Time: 19 April 2018, 12:02:35.661622 pm
UUID: 0c2401e3-1450-4f73-8e81-958f50171595
Ancestors: VMMaker.oscog- nice.2366
** new primitive to compare strings (slang + JIT)
answers negative smi, 0 or positive smi (instead of 1, 2 or 3 in the
MiscPlugin)
* Slang
> On 10 Apr 2019, at 11:42, Cyril Ferlicot wrote:
>
> On Wed, Apr 10, 2019 at 10:42 AM Stéphane Ducasse
> mailto:stephane.duca...@inria.fr>> wrote:
>>
>> Hi
>>
>> I recall that clement told me that returning 1,2 or 3 instead of negative,
>> zero, positive was slow.
>> And I wonder if the
On Wed, Apr 10, 2019 at 10:42 AM Stéphane Ducasse
wrote:
>
> Hi
>
> I recall that clement told me that returning 1,2 or 3 instead of negative,
> zero, positive was slow.
> And I wonder if the primitive got change to the logic clement proposed?
>
> Could we not introduce another primitive and use
There is a new Pharo build available!
The status of the build #217 was: SUCCESS.
The Pull Request #3116 was integrated:
"3006-When-a-test-fails-open-the-debugger-on-the-test-instead-of-on-Objectassert"
Pull request url: https://github.com/pharo-project/pharo/pull/3116
Issue Url:
Hi
I recall that clement told me that returning 1,2 or 3 instead of negative,
zero, positive was slow.
And I wonder if the primitive got change to the logic clement proposed?
Could we not introduce another primitive and use it from the image?
compare: string1 with: string2 collated: order
There is a new Pharo build available!
The status of the build #216 was: FAILURE.
The Pull Request #3141 was integrated: "3140-Fixing-all-executable-comments"
Pull request url: https://github.com/pharo-project/pharo/pull/3141
Issue Url: https://github.com/pharo-project/pharo/issues/3140
Build
Hi,
Time to time I hear people like Richard saying “Dolphin is the dialect most
beautiful Smalltalk he used” and others praising it in different levels.
As Pharo “architect” (or whatever I am, but at least I’m sure I have to pay
attention to the IDE :P), I’m interested to know what elements of
24 matches
Mail list logo
