September 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] OSProcess for Pharo3.0

by Goubier Thierry

Le 02/09/2013 12:02, StÃ©phane Ducasse a Ã©crit : > ok I read the big thread and what would be a solution? Updating OSProcess? It's just that the code which does the platform selection is already quite interesting due to platform differences, and I'm not sure how I should update it for Pharo3. Suggestions? OSProcess class>>osVersion osVersion "After Squeak version 3.6, #osVersion was moved to SmalltalkImage. Some versions of Pharo move this to OSPlatform and issue deprecation warnings about the other usages." "self osVersion" ^ (((Smalltalk hasClassNamed: #OSPlatform) and: [(Smalltalk at: #OSPlatform) respondsTo: #osVersion]) ifTrue: [Smalltalk at: #OSPlatform] ifFalse: [((Smalltalk classNamed: 'SmalltalkImage') ifNil: [^ Smalltalk osVersion]) current]) osVersion Thierry > On Sep 2, 2013, at 11:20 AM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > >> Hi, >> >> sometimes during the summer, a method used by OSProcess to determine the OS Platform has been deprecated in Pharo 3.0. Is it possible to have a look into updating OSProcess? >> >> I'm still unable to use Pharo3.0 because of issue 11102, but I'd like to get gitfiletree to work on it, and I think the main issue is OSProcess. >> >> Thanks, >> >> Thierry >> -- >> Thierry Goubier >> CEA list >> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >> 91191 Gif sur Yvette Cedex >> France >> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >> > > > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Sept. 2, 2013

Re: [Pharo-dev] Smacc question

by Goubier Thierry

Hi Stef, I don't see unsupported syntax, just missing quotes around some tokens, such as ** should be "**", + should be "+" in binary_adding_operator, etc... BOOLEAN is probably <BOOLEAN> Are you sure that the text you're joining isn't unquoted? It's hard to requote everything as it should be, and not having the lexer definition makes testing with SmaCC a bit painfull. Thierry Le 02/09/2013 12:18, StÃ©phane Ducasse a Ã©crit : > Hi thierry > > I imported the generated parsers (a student did a while ago on VW using Smacc). > The generated parser parse apparently the tests. > Now when I regenerate the parser with Pharo I cannot get the Smacc compuling the parser. > I get a SmaCCParserError: Token not expected > > do you have any idea what would not be supported in the Pharo/Squeak version > > > # > # Expression Parser > #============================================= > > goal: expression* ; > > expression: relation > ( ( > and > | > and then > | > or > | > or else > | > xor > ) relation )*; > > relation: simple_expression > sndPart?; > > sndPart: relational_operator simple_expression | > ( > not > )? ( > in range > | > in > type_mark); > > simple_expression: (unary_adding_operator)? > term (binary_adding_operator term)*; > > term: factor (multiplying_operator factor)*; > > factor: primary ( > ** > primary)? | > abs > primary | > not > primary; > > #<identifier> instead of name > primary: <numeric_lit> | > null > | <string_lit> | <number> | > <identifier> | <identifier> > '' > <identifier> | > function_call | > ( > expression > ) > ; > #simplified > > binary_adding_operator: > + > | > - > | > & > ; > unary_adding_operator: > + > | > - > ; > multiplying_operator: > * > | > / > | > mod > | > rem > ; > relational_operator: > = > | > /= > | > < > | > <= > | > > > | > >= > ; > > #============================================================================= > > function_call: <identifier> ''identifier'' function_arguments ''args'' > { ADFunctionCall withElements: args withName: identifier } ; > > function_arguments: > ( > expression ( > , > expression)* > ) > ; > > #==== Declarations =========================================================== > > discrete_range: range | subtype_indication; #discrete_? > > subtype_indication: type_mark (constraint)? ; > > type_mark: type; > > constraint: range_constraint; > > range_constraint: > range > range; > > range: range_attribute | (simple_expression > .. > simple_expression); > > range_attribute: <identifier> > '' > > range > ; #cf. 4.1.4 > > #==== Names ================================================================== > > name: simple_name | <char_lit> | > indexed_component | > slice | selected_component | > attribute; #operator_symbol > > prefix: name | function_call; > > simple_name: <identifier>; > > indexed_component: prefix > ( > expression ( > , > expression )* > ) > ; > > slice: prefix > ( > discrete_range > ) > ; > > selected_component: prefix > . > selector; > > selector: simple_name | <char_lit> | > > all > ; #operator_symbol > > attribute: prefix > '' > attribute_designator; > > attribute_designator: simple_name ( > ( > <universal_static_expression> > ) > )? ; > > #==== Types: appendix c: package STANDARD plus more ========================================================= > type: > BOOLEAN > | > REAL > | > INTEGER > | > FLOAT > | > CHARACTER > | > DURATION > | > > STRING > | > RAINBOW > ; > > ' > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Sept. 2, 2013

Smacc question

by StÃ©phane Ducasse

Hi thierry I imported the generated parsers (a student did a while ago on VW using Smacc). The generated parser parse apparently the tests. Now when I regenerate the parser with Pharo I cannot get the Smacc compuling the parser. I get a SmaCCParserError: Token not expected do you have any idea what would not be supported in the Pharo/Squeak version # # Expression Parser #============================================= goal: expression* ; expression: relation ( ( and | and then | or | or else | xor ) relation )*; relation: simple_expression sndPart?; sndPart: relational_operator simple_expression | ( not )? ( in range | in type_mark); simple_expression: (unary_adding_operator)? term (binary_adding_operator term)*; term: factor (multiplying_operator factor)*; factor: primary ( ** primary)? | abs primary | not primary; #<identifier> instead of name primary: <numeric_lit> | null | <string_lit> | <number> | <identifier> | <identifier> '' <identifier> | function_call | ( expression ) ; #simplified binary_adding_operator: + | - | & ; unary_adding_operator: + | - ; multiplying_operator: * | / | mod | rem ; relational_operator: = | /= | < | <= | > | >= ; #============================================================================= function_call: <identifier> ''identifier'' function_arguments ''args'' { ADFunctionCall withElements: args withName: identifier } ; function_arguments: ( expression ( , expression)* ) ; #==== Declarations =========================================================== discrete_range: range | subtype_indication; #discrete_? subtype_indication: type_mark (constraint)? ; type_mark: type; constraint: range_constraint; range_constraint: range range; range: range_attribute | (simple_expression .. simple_expression); range_attribute: <identifier> '' range ; #cf. 4.1.4 #==== Names ================================================================== name: simple_name | <char_lit> | indexed_component | slice | selected_component | attribute; #operator_symbol prefix: name | function_call; simple_name: <identifier>; indexed_component: prefix ( expression ( , expression )* ) ; slice: prefix ( discrete_range ) ; selected_component: prefix . selector; selector: simple_name | <char_lit> | all ; #operator_symbol attribute: prefix '' attribute_designator; attribute_designator: simple_name ( ( <universal_static_expression> ) )? ; #==== Types: appendix c: package STANDARD plus more ========================================================= type: BOOLEAN | REAL | INTEGER | FLOAT | CHARACTER | DURATION | STRING | RAINBOW ; '

Sept. 2, 2013

Re: [Pharo-dev] Should Job use SystemAnnouncer?

by StÃ©phane Ducasse

thanks! Stef On Sep 2, 2013, at 12:00 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > And for 3.0 > > Issue 11520 > > Kernel-StephanEggermont.1588.mcz > Morphic-Base-StephanEggermont.85.mcz >

Sept. 2, 2013

Re: [Pharo-dev] OSProcess for Pharo3.0

by StÃ©phane Ducasse

ok I read the big thread and what would be a solution? On Sep 2, 2013, at 11:20 AM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > Hi, > > sometimes during the summer, a method used by OSProcess to determine the OS Platform has been deprecated in Pharo 3.0. Is it possible to have a look into updating OSProcess? > > I'm still unable to use Pharo3.0 because of issue 11102, but I'd like to get gitfiletree to work on it, and I think the main issue is OSProcess. > > Thanks, > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >

Sept. 2, 2013

Re: [Pharo-dev] Should Job use SystemAnnouncer?

by Stephan Eggermont

And for 3.0 Issue 11520 Kernel-StephanEggermont.1588.mcz Morphic-Base-StephanEggermont.85.mcz

Sept. 2, 2013

Re: [Pharo-dev] Thanks for the configuration Browser :)

by StÃ©phane Ducasse

On Sep 2, 2013, at 11:04 AM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > You just need a single user of Smacc in Pharo2 for that :) thanks for the maintenance of Smacc :) > > Thierry > > Le 30/08/2013 22:45, StÃ©phane Ducasse a Ã©crit : >> and for the configurations that are up to dateâ¦ >> In 3 min I could load Smacc in Pharo2.0 >> >> Stef >> > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >

Sept. 2, 2013

Re: [Pharo-dev] Should Job use SystemAnnouncer?

by Stephan Eggermont

Stef wrote: >did you notice a different between SystemAnnouncer and replacing it by another one? Yes, it made a significant difference. It did not remove enough overhead though. Job>value: was called over 100K times, doing that only every 100 increments helped enough. Job>>jobAnnouncer ^jobAnnouncer ifNil: [ jobAnnouncer := Announcer new ] Job>announce: anAnnouncementClass | announcement | announcement := anAnnouncementClass on: self. self announcer announce: announcement. Job>announcer ^Job jobAnnouncer SystemProgressMorph>>enable Job jobAnnouncer on: JobStart send: #startJob: to: self. Job jobAnnouncer on: JobEnd send: #endJob: to: self. Job jobAnnouncer on: JobChange send: #updateJob: to: self. SystemProgressMorph>>disable Job jobAnnouncer unsubscribe: self. Morphic-StephanEggermont.1375.mcz Kernel-StephanEggermont.1351.mcz

Sept. 2, 2013

OSProcess for Pharo3.0

by Goubier Thierry

Hi, sometimes during the summer, a method used by OSProcess to determine the OS Platform has been deprecated in Pharo 3.0. Is it possible to have a look into updating OSProcess? I'm still unable to use Pharo3.0 because of issue 11102, but I'd like to get gitfiletree to work on it, and I think the main issue is OSProcess. Thanks, Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Sept. 2, 2013

[update 3.0] #30363

by Marcus Denker

30363 ----- 11468 Use singleton for default FileSystem https://pharo.fogbugz.com/f/cases/11468 11498 Be able to set an initial filter in ListDialogWindow https://pharo.fogbugz.com/f/cases/11498 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Widgets-MarcusDenke… http://smalltalkhub.com/mc/Pharo/Pharo30/main/FileSystem-Disk-MarcusDenker.… http://smalltalkhub.com/mc/Pharo/Pharo30/main/FileSystem-Core-MarcusDenker.…

Sept. 2, 2013