Re: [Pharo-dev] subexpression precedence

> On Jan 11, 2017, at 9:38 PM, Martin McClure wrote: > >> On 01/11/2017 04:54 PM, Jan Vrany wrote: >> Hi, I'm afraid this is not specified. There's no >> language specification (*) as such of Pharo or any >> other available smalltalk - at least not that I know >> (prove

Re: [Pharo-dev] subexpression precedence

On 01/11/2017 04:54 PM, Jan Vrany wrote: Hi, I'm afraid this is not specified. There's no language specification (*) as such of Pharo or any other available smalltalk - at least not that I know (prove me if I'm wrong). The ANSI Smalltalk spec says "The individual statements are executed in

Re: [Pharo-dev] subexpression precedence

I think for Redline Smalltalk which is why I'm asking I'll make sure my test subexpressions yield the same result as the same subexpressions on Pharo :) On Thu, Jan 12, 2017 at 2:58 PM, Chris Muller wrote: > > Other than humans generally read from > > (pardon me) > > Other

Re: [Pharo-dev] subexpression precedence

>> a := b := c := d := 4 This one is straight forward but subexpressions, those with () around them are the topic. On Thu, Jan 12, 2017 at 2:54 PM, Chris Muller wrote: > > Wow, I just skimmed the messages section in the blue book and you're > right. I think this is an

Re: [Pharo-dev] subexpression precedence

> Other than humans generally read from (pardon me) Other than that the code is read from left to right...

Re: [Pharo-dev] subexpression precedence

> Wow, I just skimmed the messages section in the blue book and you're right. > I think this is an omission and that it should be specified that keyword > message receiver and arguments are evaluated strictly left-to-right. I don't > know of a Smalltalk implementation that doesn't evaluate in

Re: [Pharo-dev] subexpression precedence

Hi Jan, > On Jan 11, 2017, at 4:54 PM, Jan Vrany wrote: > > Hi, I'm afraid this is not specified. There's no > language specification (*) as such of Pharo or any > other available smalltalk - at least not that I know > (prove me if I'm wrong). Wow, I just skimmed the

Re: [Pharo-dev] subexpression precedence

Hi, I'm afraid this is not specified. There's no language specification (*) as such of Pharo or any  other available smalltalk - at least not that I know  (prove me if I'm wrong). Order in which subexpressions are evaluated is rarely specified. IIRC, JVM Spec doesn't specify it either. If the

[Pharo-dev] subexpression precedence

Hi Pharo People, I know Smalltalk has precedence rules when subexpressions () are involved. 2 + ( (3 * 4) - 1 ) evaluated last ( (evaluated first) evaluated second ) That is the inner most subexpression is evaluated first. Given the following made up expression for the purposes of my

Re: [Pharo-dev] Strange DNU effect on Windows with Pastell

OK, thanks, you are right; I was confused by the new filter option in senders, somehow I assumed the list was not longer (and I ignored the scroll bar) - weird. I see them now. Yes, both should be changed together. > On 11 Jan 2017, at 12:33, Henrik Nergaard wrote: > >

Re: [Pharo-dev] Strange DNU effect on Windows with Pastell

Both #head and #tail is used by MorphTreeNodeMorph (#expandPath: and #matchPath:) to select items deeper inside the tree structure and then expanding to this. - | model morph | model := ClassTreeExample new. model openOn:

[Pharo-dev] Looking for Pharo devs

Hello, Looking for someone with thorough Pharo experience for some experimental changes to the Pharo environment and language. Some areas you will expertise in: 1. Syntax parser.2. AST.3. Thorough overall environment knowledge. For more details send an e-mail to mi...@tutanota.de.

Re: [Pharo-dev] Strange DNU effect on Windows with Pastell

All good and well, but maybe its me, but I can't see where it is being used ... > On 11 Jan 2017, at 11:46, Henrik Nergaard wrote: > > And Object/Association >> #tail > > Best regards, > Henrik > > -Opprinnelig melding- > Fra: Pharo-dev

Re: [Pharo-dev] Strange DNU effect on Windows with Pastell

in general, rule of thumb when extending classes should be “use the most specific name possible”, for instance: #magritteDescription instead of #description, etc. but everybody makes mistakes… in voyage I added methods #save, #remove instead a #voyageSave, #voyageRemove… one could argue that

Re: [Pharo-dev] Call of projects of open-dev lectures

On 04/01/2017 15:48, Stephane Ducasse wrote: > Hi > > We are organising a lecture where students should > - learn pharo > - learn how to communicate with open source community > - learn how to reverse engineer, fix bugs > They should work by 3/4. > > We are looking for projects that would

Re: [Pharo-dev] Strange DNU effect on Windows with Pastell

And Object/Association >> #tail Best regards, Henrik -Opprinnelig melding- Fra: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] På vegne av Esteban Lorenzano Sendt: 11 January 2017 10:13 Til: Pharo Development List Emne: Re: [Pharo-dev] Strange DNU

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60343 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] d51704: 60343

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: d51704f977be4ab9d11b0db83377a8b9b02085d8 https://github.com/pharo-project/pharo-core/commit/d51704f977be4ab9d11b0db83377a8b9b02085d8 Author: Jenkins Build Server Date:

Re: [Pharo-dev] Strange DNU effect on Windows with Pastell

> On 11 Jan 2017, at 10:12, Esteban Lorenzano wrote: > > at least we should rename it as “treeMorphHead”… just “head” is too generic. “treeNodeHead” I meant. > > Esteban > > >> On 11 Jan 2017, at 10:03, Sven Van Caekenberghe wrote: >> >> >>> On 11

Re: [Pharo-dev] Strange DNU effect on Windows with Pastell

at least we should rename it as “treeMorphHead”… just “head” is too generic. Esteban > On 11 Jan 2017, at 10:03, Sven Van Caekenberghe wrote: > > >> On 11 Jan 2017, at 09:55, Torsten Bergmann wrote: >> >>> But why the hell would there be a Object>>#head ?!

Re: [Pharo-dev] Strange DNU effect on Windows with Pastell

> On 11 Jan 2017, at 09:55, Torsten Bergmann wrote: > >> But why the hell would there be a Object>>#head ?! >> >> IMHO such general selectors at this level should not be used unless there is >> a very good reason to do so. >> > > Yes - some Morphic addition. Version says:

Re: [Pharo-dev] Strange DNU effect on Windows with Pastell

> But why the hell would there be a Object>>#head ?! > > IMHO such general selectors at this level should not be used unless there is > a very good reason to do so. > Yes - some Morphic addition. Version says: BenjaminVanRyseghem in 2013 Only used in MorphTreeNodeMorph and to me this smells.

Re: [Pharo-dev] Strange DNU effect on Windows with Pastell

> On 11 Jan 2017, at 09:33, Torsten Bergmann wrote: > > I've found it: > > Loading Pastell into latest image 60342 using: > > >Metacello new > smalltalkhubUser: 'Pharo' project: 'MetaRepoForPharo50'; > configuration: 'Pastell'; > version:

Re: [Pharo-dev] Strange DNU effect on Windows with Pastell

I've found it: Loading Pastell into latest image 60342 using: Metacello new smalltalkhubUser: 'Pharo' project: 'MetaRepoForPharo50'; configuration: 'Pastell'; version: #stable; load. the tests are green now. And it is also not a difference

Re: [Pharo-dev] Which package includes GVGraphViz?

I don't know which package includes GV GraphViz classes, but in the current Tool-DependencyAnalysis there are missing/moved methods (like #ifGraphVizAbsent:). If you want to generate GraphViz visualizations (assuming you have GraphViz installed and binary path added in your PATH variable) you may

[Pharo-dev] Strange DNU effect on Windows with Pastell

I have a strange effect I was not able to find out so far. You can try with any newer Pharo image/VM but here are the exact combination I tried: 1. Load latest VM from https://dl.bintray.com/pharo-project/pharo-vm/ which is as of today