November 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Running without sources/changes ?

by Sven Van Caekenberghe

> On 04 Nov 2015, at 14:14, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 03 Nov 2015, at 17:15, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Hi, >> >> Does anyone know if we can still run Pharo (4) without sources and without changes ? Years ago there used to be an option to 'abandon changes' and/or 'abandon sources', IIRC. Can we still do that ? I can't find this option in System Settings. I want to run just a reduced image on a server. >> > > No, in Pharo4 it does not workâ¦ we should have a look again, if we have the time. > > What is clear is that we really need to find a better solution to .changes/.sourcesâ¦ > > Marcus It would be good to have this functionality back, but it is not a high priority. But in 4.0 even #cleanupForProduction did not work ... It did not make that much size difference anyway, so again, no high priority. Sven

Nov. 8, 2015

Re: [Pharo-dev] code repository options

by Dale Henrichs

On 11/7/15 9:52 AM, Thierry Goubier wrote: > Le 07/11/2015 18:30, Sean P. DeNigris a Ã©crit : >> Thierry Goubier wrote >>> Has it an effect that you loose access to some of the >>> versions of your packages when you delay committing with git + >>> filetree? >> >> I usually just delay the commit in order to save all packages related >> to a >> feature, not to save multiple versions of the same package, so I >> haven't run >> into that yet. > > Hum. > > There is this behavior in GitFileTree (saving multiple packages with > one commit) but it is only active when you save a package and its > dependencies (as in a Slice). > > In short, yes, it would be easy to automate if the right concepts and > actions were available above the repository. As usual :( > > Thierry For tODE, I manage commits and loads, reverts, etc. at the Metacello project level - all dirty packages in a project are committed at once ... you can revert a project and all dirty packages are reverted, merging, etc .... There's a certain amount that can be done through the Metacello api, but I've ended up building a "project model" that wraps Metacello ... Dale

Nov. 8, 2015

Re: [Pharo-dev] Woe unto thee who assigns to class-side #name!

by Ben Coman

On Sun, Nov 8, 2015 at 1:21 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Issue 16947: Class-side Inst Var "#name" Allowed, But Breaks System > https://pharo.fogbugz.com/f/cases/16947/Class-side-Inst-Var-name-Allowed-Bu… > > If you like adventure, try the following: > class := Object subclass: #MyClass > instanceVariableNames: '' > classVariableNames: '' > category: 'MyBug'. > class class compile: 'break name := 1'. > class break. > MyClass browse > > "Emergency evaluator :/" > > To restore the system: > class instVarNamed: #name put: #MyClass. > > Now here's the kicker - there doesn't seem to a class-side instVarNamed: > #name! It's not defined in Object or ProtoObject. > > NB. Also a bug in Pharo 4.0 But Class has an instance variable 'name', and Class subclasses --> {ProtoObject class} Following on from past discussions about making the generic 'name' identifier available to applications, should that instance variable and accessors be renamed to 'classname' ? I don't know at all whether that would be a good idea, I just raise the question. cheers -ben

Nov. 8, 2015

Re: [Pharo-dev] Code critic very bugged ?

by Dimitris Chloupis

ah I forgot about that one, yes it does here it is http://pastebin.com/uW4AMphu On Sun, Nov 8, 2015 at 1:37 PM Nicolai Hess <nicolaihess(a)gmail.com> wrote: > 2015-11-08 12:27 GMT+01:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: > >> Hey guys I try to use shortcuts and arrow keys with nautilus and I get >> this every time >> >> MNU : receiver of doSemanticsAnalysis: is nil >> >> in ASTCache at: aCompiledMethod >> >> I would paste the full stack but it keeps throwing me MNUs when I try to >> do anything with the debugger. Seems like a pretty major bug , am I the >> only one experiencing this ? >> > > does the pharodebug.log contain the stack trace? > > > >> >> I am on macos Yosemite using latest pharo 5 image and stable vm with >> >> wget -O- get.pharo.org/50+vm | bash >> >> >>

Nov. 8, 2015

Re: [Pharo-dev] Code critic very bugged ?

by Nicolai Hess

2015-11-08 12:27 GMT+01:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: > Hey guys I try to use shortcuts and arrow keys with nautilus and I get > this every time > > MNU : receiver of doSemanticsAnalysis: is nil > > in ASTCache at: aCompiledMethod > > I would paste the full stack but it keeps throwing me MNUs when I try to > do anything with the debugger. Seems like a pretty major bug , am I the > only one experiencing this ? > does the pharodebug.log contain the stack trace? > > I am on macos Yosemite using latest pharo 5 image and stable vm with > > wget -O- get.pharo.org/50+vm | bash > > >

Nov. 8, 2015

Code critic very bugged ?

by Dimitris Chloupis

Hey guys I try to use shortcuts and arrow keys with nautilus and I get this every time MNU : receiver of doSemanticsAnalysis: is nil in ASTCache at: aCompiledMethod I would paste the full stack but it keeps throwing me MNUs when I try to do anything with the debugger. Seems like a pretty major bug , am I the only one experiencing this ? I am on macos Yosemite using latest pharo 5 image and stable vm with wget -O- get.pharo.org/50+vm | bash

Nov. 8, 2015

[ANN] No-Metadata mode for GitFileTree

by Thierry Goubier

Oh yes, I can announce that from now on, the development version of GitFileTree for Pharo 5 handles FileTree repositories without most of the metadata (precisely version and methodProperties). This makes the format a lot more DVCS friendly (Git, Fossil, Hg, SVN, all...) by cutting the noise on diffs and conflicts on merge and cherry picking. Note: it only apply to brand new repositories; nothing is changed for pre-existing ones. Note2: reading those Metadata-less repositories with FileTree does give you packages without metadata: no version history, no author, no author nor timestamp on methods. Note3: it is possible to hack a repo from metadata to non-metadata mode, but I won't explain it. Enjoy and tell me how it works for you. I'm especially interested by heavy branchers/mergers reports :) Thierry

Nov. 7, 2015

Re: [Pharo-dev] code repository options

by Thierry Goubier

Le 07/11/2015 18:30, Sean P. DeNigris a Ã©crit : > Thierry Goubier wrote >> Has it an effect that you loose access to some of the >> versions of your packages when you delay committing with git + filetree? > > I usually just delay the commit in order to save all packages related to a > feature, not to save multiple versions of the same package, so I haven't run > into that yet. Hum. There is this behavior in GitFileTree (saving multiple packages with one commit) but it is only active when you save a package and its dependencies (as in a Slice). In short, yes, it would be easy to automate if the right concepts and actions were available above the repository. As usual :( Thierry

Nov. 7, 2015

Re: [Pharo-dev] Woe unto thee who assigns to class-side #name!

by Thierry Goubier

Le 07/11/2015 18:21, Sean P. DeNigris a Ã©crit : > Issue 16947: Class-side Inst Var "#name" Allowed, But Breaks System > https://pharo.fogbugz.com/f/cases/16947/Class-side-Inst-Var-name-Allowed-Bu… > > If you like adventure, try the following: > class := Object subclass: #MyClass > instanceVariableNames: '' > classVariableNames: '' > category: 'MyBug'. > class class compile: 'break name := 1'. > class break. > MyClass browse > > "Emergency evaluator :/" > > To restore the system: > class instVarNamed: #name put: #MyClass. > > Now here's the kicker - there doesn't seem to a class-side instVarNamed: > #name! It's not defined in Object or ProtoObject. When I try that, I can avoid the emergency evaluator if I try to browse with an already opened system browser -> I get a red window instead with a Metaclass>>#name problem. Thierry > NB. Also a bug in Pharo 4.0 > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Woe-unto-thee-who-assigns-to-class-side-name-tp485973… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

Nov. 7, 2015

[pharo-project/pharo-core] 5bd3e3: 50425

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 5bd3e314be04b64f703de53c39fe0884b855de62 https://github.com/pharo-project/pharo-core/commit/5bd3e314be04b64f703de53c… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-11-07 (Sat, 07 Nov 2015) Changed paths: M Refactoring-Critics.package/RBSmalllintChecker.class/class/instance creation/runRule_onEnvironment_.st M Refactoring-Critics.package/RBSmalllintChecker.class/instance/actions/run.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50424.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50425.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50424.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50425.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50425 16946 revert 16814: Monkey completely broken https://pharo.fogbugz.com/f/cases/16946 http://files.pharo.org/image/50/50425.zip

Nov. 7, 2015