On Tue, 5 Mar 2019 at 22:11, Alistair Grant wrote:
>
> Hi Hilaire,
>
> On Tue, 5 Mar 2019 at 21:16, Hilaire wrote:
> >
> > Alistair,
> >
> > I checked, the error shows under this specific situation I described in
> > my previous email.
>
> I figured out the environment that caused the primtiveFai
On 5/3/19 17:59, Craig Johnson wrote:
>
> Hi All,
>
>
>
> I was trying to figure an elegant way to slice strings (Python style),
> and came up empty.
>
>
>
> What is the simplest way to copy characters between positions 4 and 8
> from a string in Pharo?
>
>
>
> Craig
>
You can use:
'String
Thanks a lot Michel.
I will see if there is any way to port this to Arch/Manjaro.
Cheers,
Offray
On 3/3/19 11:52, Michael Zeder wrote:
> Hi!
> I would like to make two offers:
> First, I know, deciding to be provocative can hurt. I did it int the
> hope that the released energy will be transfor
Hi All,
I was trying to figure an elegant way to slice strings (Python style), and came
up empty.
What is the simplest way to copy characters between positions 4 and 8 from a
string in Pharo?
Craig
Hi Hilaire,
On Tue, 5 Mar 2019 at 21:16, Hilaire wrote:
>
> Alistair,
>
> I checked, the error shows under this specific situation I described in
> my previous email.
I figured out the environment that caused the primtiveFailure and can
see how my modified code avoids the issue.
> Yes, your co
Cool.
Le 05/03/2019 à 18:04, peter yoo a écrit :
> ok. today me tested again. maybe my XIM env is bad before. is ok now.
> thanks to all.
> all fcitx package remove and re-install. and ok...
>
> 감사합니다. for pharo users. :D
--
Dr. Geo
http://drgeo.eu
Alistair,
I checked, the error shows under this specific situation I described in
my previous email.
Yes, your code fixes this condition, the condense does not hit this
error anymore.
Thanks
Hilaire
Le 05/03/2019 à 17:59, Alistair Grant a écrit :
> I've attached a change-set that fixes #nextVe
Hi Holger,
> My plan of action is to start with a protobuf compiler/model and then look
> into binding the gRPC C implementation to Pharo.
I have an almost complete parser and compiler (class generation)
implementation of protobuf in Pharo around somewhere...
I cant quite remember the state of i
On 5 Mar 2019, at 19:22, Mariano Martinez Peck wrote:
On Tue, Mar 5, 2019 at 1:42 PM Konrad Hinsen
wrote:
Hi everyone,
does anyone here have some experience with Fuel?
Its Web site says "It can serialize/materialize not only plain
objects
but also classes, traits, methods, closures, cont
On Tue, Mar 5, 2019 at 1:42 PM Konrad Hinsen
wrote:
> Hi everyone,
>
> does anyone here have some experience with Fuel?
>
> Its Web site says "It can serialize/materialize not only plain objects
> but also classes, traits, methods, closures, contexts, packages,
> etc.". So I should be able to ser
ok. today me tested again. maybe my XIM env is bad before. is ok now.
thanks to all.
all fcitx package remove and re-install. and ok...
감사합니다. for pharo users. :D
Hi Hilaire,
On Tue, 5 Mar 2019 at 15:09, HilaireFernandes wrote:
>
> The problem seems to happen when there is the following conditions, in the
> folder containing the image:
>
> - there is a drgeo file, in my situation it is a link to the DrGeo
> repository
> - the image name is drgeo.image, ...
Hi everyone,
does anyone here have some experience with Fuel?
Its Web site says "It can serialize/materialize not only plain objects
but also classes, traits, methods, closures, contexts, packages,
etc.". So I should be able to serialize a class somehow, right?
But classes are by default treated
The problem seems to happen when there is the following conditions, in the
folder containing the image:
- there is a drgeo file, in my situation it is a link to the DrGeo
repository
- the image name is drgeo.image, ...
- PharoCondense is executed, then FileRefrence>>nextVersion seems confused
by t
14 matches
Mail list logo