Back to the thread: https://github.com/pharo-project/pharo/pull/440
2017-11-06 22:52 GMT+01:00 Ben Coman :
>
>
> On Tue, Nov 7, 2017 at 4:52 AM, Nicolas Cellier gmail.com> wrote:
>
>>
>>> MC is not so bad. OK branches are not named (or neeed not be), GUID are
>> inferior to SHA, etc...
>> The bi
2017-11-06 20:52 GMT+01:00 Stephane Ducasse :
> Esteban told me that this is because he uses STON for the class definition.
> Now a simple question may be we could use a string instead of a symbol
> because this is strange
> to have a class definitino that does not respect Pharo syntax.
>
But any
On Tue, Nov 7, 2017 at 4:52 AM, Nicolas Cellier <
nicolas.cellier.aka.n...@gmail.com> wrote:
>
>> MC is not so bad. OK branches are not named (or neeed not be), GUID are
> inferior to SHA, etc...
> The biggest difference comes from github, that is the social environment,
> not necessarily git.
>
> On 6 Nov 2017, at 20:52, Stephane Ducasse wrote:
>
> Esteban told me that this is because he uses STON for the class definition.
> Now a simple question may be we could use a string instead of a symbol
> because this is strange
> to have a class definitino that does not respect Pharo syntax.
2017-11-06 18:39 GMT+01:00 Martin Dias :
>
>
> On Mon, Nov 6, 2017 at 10:20 AM, Nicolas Cellier <
> nicolas.cellier.aka.n...@gmail.com> wrote:
>
>>
>>
>> Pharo still has Monticello, so it could have worked (not sure how well
>> without common ancestor)
>> The extra difficulty here is that package
On Mon, Nov 6, 2017 at 9:52 PM, Nicolas Cellier
wrote:
>
>
> 2017-11-06 21:04 GMT+01:00 Stephane Ducasse :
>>
>> Hi nicolas
>>
>> While I know the ascending and other protocol, it is still unclear to
>> me the composition aspect. Did Travis write a tutorial
>> can we can use as documentation/comme
2017-11-06 21:04 GMT+01:00 Stephane Ducasse :
> Hi nicolas
>
> While I know the ascending and other protocol, it is still unclear to
> me the composition aspect. Did Travis write a tutorial
> can we can use as documentation/comment?
>
> BTW
> "Example: #('abc' 'de' 'fghi') sorted: #size asscendin
Hi nicolas
While I know the ascending and other protocol, it is still unclear to
me the composition aspect. Did Travis write a tutorial
can we can use as documentation/comment?
BTW
"Example: #('abc' 'de' 'fghi') sorted: #size asscending"
=>
"Example: (#('abc' 'de' 'fghi') sorted: #size) ascend
Esteban told me that this is because he uses STON for the class definition.
Now a simple question may be we could use a string instead of a symbol
because this is strange
to have a class definitino that does not respect Pharo syntax.
Stef
On Mon, Nov 6, 2017 at 8:15 PM, Dale Henrichs
wrote:
>
>
On 11/06/2017 08:23 AM, Sven Van Caekenberghe wrote:
On 6 Nov 2017, at 17:13, Dale Henrichs wrote:
On 11/6/17 7:07 AM, Sven Van Caekenberghe wrote:
On 6 Nov 2017, at 15:43, Dale Henrichs wrote:
of course with Pharo's implementation of Symbol it is not practical to use
asString nor typ
2017-11-06 18:20 GMT+01:00 Sven Van Caekenberghe :
>
>
> > On 6 Nov 2017, at 17:25, Nicolas Cellier l.com> wrote:
> >
> >
> >
> > 2017-11-06 17:23 GMT+01:00 Sven Van Caekenberghe :
> >
> >
> > > On 6 Nov 2017, at 17:13, Dale Henrichs com> wrote:
> > >
> > >
> > >
> > > On 11/6/17 7:07 AM, Sven V
On Mon, Nov 6, 2017 at 10:20 AM, Nicolas Cellier <
nicolas.cellier.aka.n...@gmail.com> wrote:
>
>
> 2017-11-06 10:51 GMT+01:00 Sven Van Caekenberghe :
>
>>
>>
>> > On 6 Nov 2017, at 10:37, Nicolas Cellier > l.com> wrote:
>> >
>> > Because it's a cross dialect library and because contributing in Sq
> On 6 Nov 2017, at 17:25, Nicolas Cellier
> wrote:
>
>
>
> 2017-11-06 17:23 GMT+01:00 Sven Van Caekenberghe :
>
>
> > On 6 Nov 2017, at 17:13, Dale Henrichs
> > wrote:
> >
> >
> >
> > On 11/6/17 7:07 AM, Sven Van Caekenberghe wrote:
> >>
> >>> On 6 Nov 2017, at 15:43, Dale Henrichs
>
Hi Nicolas,
I understand.
And I can confirm that the Squeak 64 bit/win VM SqueakSSL.dll works when
copied in the Pharo 64 bit/win folder.
Thanks for the patience
Raffaello
On 2017-11-06 17:21, Nicolas Cellier wrote:
No matter which step fails, the build is considered failed if return
co
Can this be dealt with by Quality Assistant? Special rules when in a
particular group of classes? i.e. BaselineX
cheers -ben
On Mon, Nov 6, 2017 at 10:43 PM, Dale Henrichs <
dale.henri...@gemtalksystems.com> wrote:
> ...also note that I have seen a number of baselines where symbols are used
2017-11-06 17:23 GMT+01:00 Sven Van Caekenberghe :
>
>
> > On 6 Nov 2017, at 17:13, Dale Henrichs
> wrote:
> >
> >
> >
> > On 11/6/17 7:07 AM, Sven Van Caekenberghe wrote:
> >>
> >>> On 6 Nov 2017, at 15:43, Dale Henrichs com> wrote:
> >>>
> >>> of course with Pharo's implementation of Symbol it
> On 6 Nov 2017, at 17:13, Dale Henrichs
> wrote:
>
>
>
> On 11/6/17 7:07 AM, Sven Van Caekenberghe wrote:
>>
>>> On 6 Nov 2017, at 15:43, Dale Henrichs
>>> wrote:
>>>
>>> of course with Pharo's implementation of Symbol it is not practical to use
>>> asString nor type checks - things th
No matter which step fails, the build is considered failed if return code
differs from 0...
2017-11-06 15:23 GMT+01:00 Raffaello Giulietti <
raffaello.giulie...@lifeware.ch>:
> Hi Nicolas,
>
> seems that only the upload to the Pharo repo fails, not the building by
> itself.
>
> But the cog_win64x
On 11/6/17 7:07 AM, Sven Van Caekenberghe wrote:
On 6 Nov 2017, at 15:43, Dale Henrichs wrote:
of course with Pharo's implementation of Symbol it is not practical to use
asString nor type checks - things that are not necessary in other Smalltalk
implementations
How so ?
What is the prob
> On 6 Nov 2017, at 15:43, Dale Henrichs
> wrote:
>
> of course with Pharo's implementation of Symbol it is not practical to use
> asString nor type checks - things that are not necessary in other Smalltalk
> implementations
How so ?
What is the problem with Symbol>>#asString ?
#foo asStr
...also note that I have seen a number of baselines where symbols are
used in places where Strings are required ... of course with Pharo's
implementation of Symbol it is not practical to use asString nor type
checks - things that are not necessary in other Smalltalk
implementations ... In Metac
Hi Nicolas,
seems that only the upload to the Pharo repo fails, not the building by
itself.
But the cog_win64x64_pharo.stack.spur_201711061254.zip is not even on
the bintray repo. I would expect it at least there. Is that right? Just
wondering...
Of course, I'll try to grab the SqueakSSL.d
Unfortunately, the VM is corectly built, but the script fails at deploy
stage...
https://ci.appveyor.com/project/OpenSmalltalk/vm/branch/Cog/job/gx20b215gls5jq7w
Uploading ./pharo-win-x86_64-201711061254-f819c8f.zip to
pharo.files.org//appli/files.pharo.org/vm/pharo-spur64/win
Warning: Permanently
2017-11-06 10:51 GMT+01:00 Sven Van Caekenberghe :
>
>
> > On 6 Nov 2017, at 10:37, Nicolas Cellier gmail.com> wrote:
> >
> > Because it's a cross dialect library and because contributing in Squeak
> is so much easier for me.
> >
> > I like the social power provided by github and i know how to us
Maybe create a symlink by now?
On Mon, Nov 6, 2017 at 7:24 AM, Esteban Lorenzano
wrote:
>
>
> > On 5 Nov 2017, at 11:48, Sean P. DeNigris wrote:
> >
> > I have a problem I'm not sure how to solve. In many of my baselines for
> > personal private projects, I have dependencies with filetree URL
>
There is a new Pharo build available!
The status of the build #262 was: SUCCESS.
The Pull Request #436 was integrated: "20520 Package "OpalTools" should be
"OpalCompiler-Tools""
Pull request url: https://github.com/pharo-project/pharo/pull/436
Issue Url: https://pharo.fogbugz.com/f/case
There is a new Pharo build available!
The status of the build #261 was: SUCCESS.
The Pull Request #434 was integrated: "Stupid use of asLayoutFrame should be
eliminated first pass."
Pull request url: https://github.com/pharo-project/pharo/pull/434
Issue Url: https://pharo.fogbugz.com/f/
There is a new Pharo build available!
The status of the build #260 was: SUCCESS.
The Pull Request #433 was integrated: "20640 Categorize uncategorized methods
in classes starting with "P""
Pull request url: https://github.com/pharo-project/pharo/pull/433
Issue Url: https://pharo.fogbugz
Thanks Nicolas!
On 2017-11-06 11:30, Nicolas Cellier wrote:
Oh yes, you're right,
the SqueakSLL could have been built but was not built in pharo...
I just changed
https://github.com/OpenSmalltalk/opensmalltalk-vm/edit/Cog/build.win64x64/pharo.cog.spur/plugins.ext
this should trigger another a
Oh yes, you're right,
the SqueakSLL could have been built but was not built in pharo...
I just changed
https://github.com/OpenSmalltalk/opensmalltalk-vm/edit/Cog/build.win64x64/pharo.cog.spur/plugins.ext
this should trigger another automated build and if all goes well you will
have a new bintray ar
> On 5 Nov 2017, at 11:48, Sean P. DeNigris wrote:
>
> I have a problem I'm not sure how to solve. In many of my baselines for
> personal private projects, I have dependencies with filetree URL
> repositories. IIUC, that was the best practice when I asked on the MetaC
> mailing list. The file U
Its the usual case of not being able to have your cake and eat it too.
If you want top performance you have to manage memory yourself plus the
abilitiy to access thousands of C libraries is not such a bad excuse for a
compromise. The FFI is not a problem is a solution to many problems and
people u
On 05-11-17 22:05, Stephane Ducasse wrote:
I was working in cleaning the users of asLayoutFrame and when I commit I see
- #category : 'Morphic-Base-Layouts'
+ #category : #Morphic-Base-Layouts
but #category : #Morphic-Base-Layouts
is not a valid symbol.
In Metacello we use the quoted symbol f
> On 6 Nov 2017, at 10:37, Nicolas Cellier
> wrote:
>
> Because it's a cross dialect library and because contributing in Squeak is so
> much easier for me.
>
> I like the social power provided by github and i know how to use git, at
> least as an expert beginner.
> But it took me two hours
Oh, I hope we will be able improve this process.
But personally when I set up it first time everything start to be smooth.
And when I repeat it from scratch it takes just couple of minutes.
2017-11-06 10:37 GMT+01:00 Nicolas Cellier <
nicolas.cellier.aka.n...@gmail.com>:
> Because it's a cross di
Because it's a cross dialect library and because contributing in Squeak is
so much easier for me.
I like the social power provided by github and i know how to use git, at
least as an expert beginner.
But it took me two hours to pick a pharo image, fork and clone the pharo
repository, pick a pharo
Hi Nicolas,
I tried both the vm found at the location you mention (dated 2017-10-22):
https://bintray.com/opensmalltalk/vm/download_file?file_path=cog_win64x64_pharo.cog.spur_201710221351.zip
and the "official" latest vm on the Pharo site (dated 2017-11-01)
http://files.pharo
It is difficult to compare to current Pharo version.
Why you not produce Pharo pull request?
2017-11-06 0:06 GMT+01:00 Nicolas Cellier <
nicolas.cellier.aka.n...@gmail.com>:
> I've put some of the proposed composition features into
>
> http://source.squeak.org/inbox/Collections-nice.766.mcz
> htt
Hi Ben,
It's a super bad idea to copy an ExternalAddress.
It's common knowledge in C++ copy operator & copy constructors...
But it's not obvious to me that you'll have double freeing (unless you
explicitely free the pointer by yourself).
If you use gcallocate: then only the original is registered
Hi,
[
Max replied on the Seaside ML where I originally posted:
> We don't have a build for Pharo 7 yet. Loading from github would be the
> recommended way. A quick look makes me think that it will require a bit of
> work to get the baseline set up correctly. I can't promise anything before
>
Hi Martin,
several people successfully migrated with git-migration... so I guess it
works.
> Is it good idea to move now?
There is no risk in trying to use it. If it fails, you report a bug. :-)
Is it the right tool?
Yes.
As for Tonel... git-migration uses FileTree, but I am looking into maki
Thanks, Ronie.
Cheers,
Doru
> On Nov 5, 2017, at 11:05 PM, Ronie Salgado wrote:
>
> Hi Stef,
>
> I can try to continue what Thibault started. Give me two weeks.
>
> Best regards,
> Ronie
>
> 2017-11-05 18:10 GMT-03:00 Stephane Ducasse :
> Personally now I do not care because I cannot contin
42 matches
Mail list logo
