Sorry for answering the "deadly long forgotten" post, but, anyway: it happens
at the moment of migration to ss3, I believe. I don't really remember actual
"relicensing" process, I think it was just...welll...selecting from the
drop-down list, and this time I selected another option.
If you or
Esteban,
The segfault is in the same method that I reported yesterday (with a
very reproducible test case)[1] ... also part of big 18706[2]
[1]
http://forum.world.st/segfault-fresh-Pharo5-0-download-w-pharo-VM-version-5-0-1-Wed-May-4-11-54-28-CEST-2016-gcc-4-6-3-Pro-tt4908706.html
[2]
Hi,
I tried to publish fixes to the Magritte XML package and the Smalltalk hub
is not working. I published off to our own repository. I there an ETA on
its getting fixed or an alternative repository to publish to?
Kind Regards,
Sean Glazier
> On 30 Jul 2016, at 13:14, Esteban Lorenzano wrote:
>
> hi Holger,
>
> do you have a reproducible way for this error? it happens always?
three times in a row, with the latest image. 50759 seems to be fine or I was
lucky. The difference is small/odd. Let me try the
> On 30 Jul 2016, at 13:14, Esteban Lorenzano wrote:
>
> hi Holger,
>
> do you have a reproducible way for this error? it happens always?
I have the impression that most derived 5.0 builds fail now, for example:
hi Holger,
do you have a reproducible way for this error? it happens always?
cheers,
Esteban
> On 30 Jul 2016, at 08:45, Holger Freyther wrote:
>
>
>> On 17 Mar 2016, at 22:16, Peter Uhnák wrote:
>
> Hi!
>
>
>> I got this error maybe once or twice
thanks
We should add that as an example in the package :)
Stef
Le 29/7/16 à 16:13, Casimiro - GMAIL a écrit :
If someone is in need to parse URIs, then the following regex handle it:
| regStr regex |
regStr :=
'((([a-z]\w+\:)', "Match URL protocol and
I will review anything you write.
I should redo the tutorial to get better at parsing.
Stef
Le 29/7/16 à 23:22, Thierry Goubier a écrit :
Le 29/07/2016 à 21:18, stepharo a écrit :
Thierry
I started a Smacc chapter in the PharoInProgress book.
Ok. I'll have a look if I can contribute
> On 17 Mar 2016, at 22:16, Peter Uhnák wrote:
Hi!
> I got this error maybe once or twice maybe a year ago on linux, but I had a
> lot of windows opened (like 20 or 30), and when I got back to big screen it
> was ok again.
I am now seeing this with a Pharo50 build on a