There is a new Pharo build available!
The status of the build #1124 was: SUCCESS.
The Pull Request #5554 was integrated: "fix-predebug-error"
Pull request url: https://github.com/pharo-project/pharo/pull/5554
Issue Url: https://github.com/pharo-project/pharo/issues/fix
Build Url:
> On 22 Jan 2020, at 18:29, John Brant wrote:
>
> On Jan 22, 2020, at 5:20 AM, Benoit St-Jean via Pharo-dev
> wrote:
>>
>> Who, in their right mind, would code like that? Is it a trend among younger
>> Smalltalkers while dinosaurs like me just "naturally" still use the "old
>> way" and
There is a new Pharo build available!
The status of the build #19 was: FAILURE.
Could not extract further issue information from commit message: Moving the
upload after the split for architectures
Build Url:
There is a new Pharo build available!
The status of the build #18 was: FAILURE.
The Pull Request #5268 was integrated: "Add 64 bits to the list of
architectures for test runs"
Pull request url: https://github.com/pharo-project/pharo/pull/5268
Issue Url:
On Jan 22, 2020, at 5:20 AM, Benoit St-Jean via Pharo-dev
wrote:
>
> Who, in their right mind, would code like that? Is it a trend among younger
> Smalltalkers while dinosaurs like me just "naturally" still use the "old way"
> and blocks?
Using symbols for blocks has been around for quite
There is a new Pharo build available!
The status of the build #17 was: FAILURE.
The Pull Request #5497 was integrated: "RB* and GR* should be renamed as Re*
... Rule - fixes: #5496"
Pull request url: https://github.com/pharo-project/pharo/pull/5497
Issue Url:
> On 22 Jan 2020, at 13:10, Gabriel Cotelli wrote:
>
> Hi!
>
> I see no problem in replacing the symbol usage with blocks. It's a nice
> shortcut for scripting but not a game changer.
> And I'm also in favor of being cautious before introducing new things without
> analyzing it's impact.
Hi!
I see no problem in replacing the symbol usage with blocks. It's a nice
shortcut for scripting but not a game changer.
And I'm also in favor of being cautious before introducing new things
without analyzing it's impact.
However, I see use cases for using objects polymorphic with blocks. A
Thanks I went over the list and tagged nearly all of them.
I think that P9 will be a real stabilisation phase.
S.
> On 22 Jan 2020, at 12:47, Vincent Blondeau
> wrote:
>
>
> From: "Vincent Blondeau"
> Subject: RE: [Pharo-dev] [P9] Large images tag
> Date: 22 January 2020 at 12:47:21 CET
>
--- Begin Message ---
Hi Stef,
Great idea! Here are some that could be added to the list:
https://github.com/pharo-project/pharo/issues/5478
https://github.com/pharo-project/pharo/issues/5260
https://github.com/pharo-project/pharo/issues/5191
https://github.com/pharo-project/pharo/issues/5188
--- Begin Message ---
+1000
I'm with you 110% on this one!
Who, in their right mind, would code like that? Is it a trend among
younger Smalltalkers while dinosaurs like me just "naturally" still use
the "old way" and blocks? And do we have statistics about how often that
"syntax" is used in
Hi all,
Inspired by Pablo's example, I've created a cross-platform
implemenation. Pablo's example uses Pharo.image embedded as a Windows
resource. Well, the excellent and, like Smalltalk, vastly underrated
Free Pascal has built-in cross platform support for Windows resources.
Basically I have
https://github.com/pharo-project/pharo/issues/5542
On Sun, Dec 22, 2019 at 5:12 PM Serge Stinckwich
wrote:
> Hi all,
> I'm having a look how floats are printed.
> Why we check two times if a Float is infinite ?
> A first time in:
>
> Float>>printOn: stream base: base
> ...
> self isInfinite
>
Hi all,
Iceberg supports branches named with slashes. It can pull, push, merge,
checkout…
IIRC, what does not properly work is metacello support regarding it, because
the parser of metacello urls may consider those extra “url path elements” part
of the directory to fetch the project.
Guille
Thanks pablo.
This is the typical example that even if we do not want to do things the world
is pushing us.
So good code always pays because change is the only constant.
S
> On 22 Jan 2020, at 09:59, teso...@gmail.com wrote:
>
> Yes, it is the PR creation API. I have started to add support
Hi Stef & Guille,
I received the same deprecation notice as Stef on 13 December.
I've also just seen an `IceGitHubError: Not Found` error:
IceGitHubAPI>>responseWithValidationDo:
IceGitHubAPI>>contentsWithValidationDo:
IceGitHubAPI>>jsonContentsWithValidationDo:
IceGitHubAPI>>get:
Yes, it is the PR creation API. I have started to add support to
tokens in a nice way. I can push it to the next version.
On Wed, Jan 22, 2020 at 9:55 AM ducasse wrote:
>
>
>
> > On 22 Jan 2020, at 09:48, Guillermo Polito
> > wrote:
> >
> > Did you re-clone your repository? I don’t think so…
>
> On 22 Jan 2020, at 09:48, Guillermo Polito wrote:
>
> Did you re-clone your repository? I don’t think so…
no
> Did you create a PR using Pharo’s github integration?
Yes I did this.
> Those are the only points we use Github’s API :/
Ok we found it :)
>
>> El 22 ene 2020, a las 9:13,
Did you re-clone your repository? I don’t think so…
Did you create a PR using Pharo’s github integration?
Those are the only points we use Github’s API :/
> El 22 ene 2020, a las 9:13, ducasse escribió:
>
> I was just committing to my pharo fork “….using Zinc HTTP Components 1.0
> (Pharo/9.0)
I was just committing to my pharo fork “….using Zinc HTTP Components 1.0
(Pharo/9.0) ...”
so I do not get fully get it.
If I’m the only one to receive this mail then this is ok
Guille apparently I used password else it would have failed? Can it be that my
password is not well set?
I have
> On 21 Jan 2020, at 23:56, Sven Van Caekenberghe wrote:
>
> I also like the use of symbols but more for casual code.
>
> I know using blocks can be faster, but the difference is not massive.
The difference is not only in speed.
And it is exactly why I do not like value in Object.
> What
> On 21 Jan 2020, at 23:46, Esteban Maringolo wrote:
>
> I also like the polymorphism of the #value: message, not only with Symbols
> but also with MADescriptions and many other uses.
Thanks this is exactly my point and I do not like it because this is cheap and
put the hell on tools.
Of
22 matches
Mail list logo
