Hi Guille,
> On Jan 18, 2019, at 6:04 AM, Guillermo Polito
> wrote:
>
>> On Fri, Jan 18, 2019 at 2:46 PM Ben Coman wrote:
>>
>>> On Fri, 18 Jan 2019 at 21:39, Sven Van Caekenberghe wrote:
>>>
>>> > On 18 Jan 2019, at 14:23, Guillermo Polito
>>> > wrote:
>>> >
>>> >
>>> > I think that
> On Jan 18, 2019, at 2:04 AM, Guillermo Polito
> wrote:
[snip]
>
> Well, personally I would like that getenv/setenv and getcwd setcwd support
> are not in a plugin but as a basic service provided by the vm.
+1000
> Cheers,
> Guille
Physically Based Rendering
an interesting book, using literate programming, as free book:
http://www.pbr-book.org/
> On 18 Jan 2019, at 15:57, Sean P. DeNigris via Pharo-dev
> wrote:
>
>
> From: "Sean P. DeNigris"
> Subject: Re: [ANN] New stable VM version.
> Date: 18 January 2019 at 15:57:12 CET
> To: pharo-dev@lists.pharo.org
>
>
> EstebanLM wrote
>> Enjoy
>
> Thanks! Which image versions does this
[ Save The Date ] Pharo Days 2019: Thursday April 4 & Friday April 5 @ Lille, FR
Dear members of the Pharo community,
We are happy to announce that we will be organising Pharo Days this year, in
Lille, France. This will be a two day event: Thursday April 4 & Friday April 5.
The main venue
--- Begin Message ---
EstebanLM wrote
> Enjoy
Thanks! Which image versions does this affect? I want to clear my Launcher
caches…
-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
--- End Message ---
Hi Esteban,
On Fri, 18 Jan 2019 at 14:49, Esteban Lorenzano wrote:
>
> Hi,
>
> Yes, I needed to promote a new stable version because last week’s was having
> a bug (which is not fixed).
> This one is based on the build:
>
> 201901172323-5a38b34
On Linux (Ubuntu 16.04) it's still the old VM:
$
--- Begin Message ---
>>
>> On my TODO is to make it stand-alone and provide is as a “compatibility
>> transform”, too.
>
> I have to dig because I remember that I went over all the deprecation in
> Pharo 60 and started to look at the ones that I
> could “transformified” so that we get a nice
--- Begin Message ---
>>> I think that will just overcomplicate things. Right now, all Strings in
>>> Pharo are unicode strings.
>>
>> Cool. I didn't realise that. But to be pedantic, which unicode encoding?
>> Should I presume from Sven's "UTF-8 encoding step" comment below
>> and the
--- Begin Message ---
Hi marcus
>> I simply love the dynamic rewriting this is just too cool. We should
>> systematically use it.
>> I will continue to use it in any deprecation.
>>
>
> On my TODO is to make it stand-alone and provide is as a “compatibility
> transform”, too.
I have to dig
--- Begin Message ---
There is a new Pharo build available!
The status of the build #131 was: SUCCESS.
The Pull Request #2267 was integrated:
"22887-TonelWritercreateDefaultOrganizationFrom-can-return-string"
Pull request url: https://github.com/pharo-project/pharo/pull/2267
Issue Url:
> On 18 Jan 2019, at 14:45, Ben Coman wrote:
>
>
>
> On Fri, 18 Jan 2019 at 21:39, Sven Van Caekenberghe wrote:
>
>
> > On 18 Jan 2019, at 14:23, Guillermo Polito
> > wrote:
> >
> >
> > I think that will just overcomplicate things. Right now, all Strings in
> > Pharo are unicode
On Fri, Jan 18, 2019 at 2:46 PM Ben Coman wrote:
>
>
> On Fri, 18 Jan 2019 at 21:39, Sven Van Caekenberghe wrote:
>
>>
>>
>> > On 18 Jan 2019, at 14:23, Guillermo Polito
>> wrote:
>> >
>> >
>> > I think that will just overcomplicate things. Right now, all Strings in
>> Pharo are unicode
On Fri, Jan 18, 2019 at 2:49 PM Esteban Lorenzano
wrote:
> Hi,
>
> Yes, I needed to promote a new stable version because last week’s was
> having a bug (which is not fixed).
>
not? now? :)
This version includes the following:
https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/355
Le ven. 18 janv. 2019 à 14:42, Marcus Denker a
écrit :
>
>
> > On 18 Jan 2019, at 14:26, ducasse wrote:
> >
> > I simply love the dynamic rewriting this is just too cool. We should
> systematically use it.
> > I will continue to use it in any deprecation.
> >
>
> On my TODO is to make it
On Fri, Jan 18, 2019 at 01:40:26PM +0100, Sven Van Caekenberghe wrote:
> Dave,
>
> > On 18 Jan 2019, at 01:54, David T. Lewis via Pharo-dev
> > wrote:
> >
> >
> > From: "David T. Lewis"
> > Subject: Re: [Pharo-dev] Better management of encoding of environment
> > variables
> > Date: 18
Hi,
Yes, I needed to promote a new stable version because last week’s was having a
bug (which is not fixed).
This one is based on the build:
201901172323-5a38b34
Enjoy (and please report problems)
Esteban
On Fri, 18 Jan 2019 at 21:39, Sven Van Caekenberghe wrote:
>
>
> > On 18 Jan 2019, at 14:23, Guillermo Polito
> wrote:
> >
> >
> > I think that will just overcomplicate things. Right now, all Strings in
> Pharo are unicode strings.
Cool. I didn't realise that. But to be pedantic, which
> On 18 Jan 2019, at 14:26, ducasse wrote:
>
> I simply love the dynamic rewriting this is just too cool. We should
> systematically use it.
> I will continue to use it in any deprecation.
>
On my TODO is to make it stand-alone and provide is as a “compatibility
transform”, too.
So we
> On 18 Jan 2019, at 14:23, Guillermo Polito wrote:
>
>
> I think that will just overcomplicate things. Right now, all Strings in Pharo
> are unicode strings. Characters are represented with their corresponding
> unicode codepoint.
> If all characters in a string have codepoints < 256 then
Le ven. 18 janv. 2019 à 14:35, ducasse a écrit :
>
> What's important is to create abstract layers that insulate the un-needed
> complexity in lowest layers possible.
> The VM excels at insulating of course.
> At image side we have to assume the responsibility of not leaking too much
> by
--- Begin Message ---
I simply love the dynamic rewriting this is just too cool. We should
systematically use it.
I will continue to use it in any deprecation.
Now I have a simple question (You can explain it to me over lunch one of these
days).
I do not get why RBAST would not be a good
On Fri, Jan 18, 2019 at 1:48 PM Ben Coman via Pharo-dev <
pharo-dev@lists.pharo.org> wrote:
>
>
>
>
> On Wed, 16 Jan 2019 at 18:37, Sven Van Caekenberghe wrote:
>
>> Still, one of the conclusions of previous discussions about the encoding
>> of environment variables was/is that there is no
--- Begin Message ---
> On 11 Jan 2019, at 20:28, Eliot Miranda wrote:
>
> Hi Thomas,
>
> forgive me, my first response was too terse. Having thought about it in the
> shower it becomes clear :-)
>
>> On Jan 11, 2019, at 6:49 AM, Thomas Dupriez
>> wrote:
>>
>> Hi,
>>
>> Yes, my
Le mer. 16 janv. 2019 à 23:23, Eliot Miranda a
écrit :
>
> Hi Sven,
>
> On Wed, Jan 16, 2019 at 2:37 AM Sven Van Caekenberghe
> wrote:
>
>> Still, one of the conclusions of previous discussions about the encoding
>> of environment variables was/is that there is no single correct solution.
>>
--- Begin Message ---
On Wed, 16 Jan 2019 at 18:37, Sven Van Caekenberghe wrote:
> Still, one of the conclusions of previous discussions about the encoding
> of environment variables was/is that there is no single correct solution.
> OS's are not consistent in how the encoding is done in all
Dave,
> On 18 Jan 2019, at 01:54, David T. Lewis via Pharo-dev
> wrote:
>
>
> From: "David T. Lewis"
> Subject: Re: [Pharo-dev] Better management of encoding of environment
> variables
> Date: 18 January 2019 at 01:54:34 GMT+1
> To: Pharo Development List
>
>
> On Thu, Jan 17, 2019 at
--- Begin Message ---
There is a new Pharo build available!
The status of the build #130 was: FAILURE.
The Pull Request #2266 was integrated:
"22896-Creating-methods-in-a-subclass-with-a-class-using-a-trait"
Pull request url: https://github.com/pharo-project/pharo/pull/2266
Issue Url:
--- Begin Message ---
>
> So making the primitives return ByteArray instances instead of ByteString
> should be safe enough :).
> But this is in my opinion clearly a hack instead of fixing the real problem,
> and we have to be careful to guard such patterns with comments everywhere
>
--- Begin Message ---
> >
> > And if it's in the image you get to do the programming in Smalltalk rather
> > than C or Slang, which is more fun for most of us. And, let's face it, fun
> > is an important metric in an open-source project -- things that are fun are
> > much more likely to get
On Fri, Jan 18, 2019 at 1:58 AM David T. Lewis via Pharo-dev <
pharo-dev@lists.pharo.org> wrote:
> On Thu, Jan 17, 2019 at 04:57:18PM +0100, Sven Van Caekenberghe wrote:
> >
> > > On 16 Jan 2019, at 23:23, Eliot Miranda
> wrote:
> > >
> > > On Wed, Jan 16, 2019 at 2:37 AM Sven Van Caekenberghe
31 matches
Mail list logo
