- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] how i can browse the users of some trait?

by Igor Stasenko

and as follow-up, why we need such trait if it has only one user??? On 3 December 2013 13:30, Igor Stasenko <siguctua(a)gmail.com> wrote: > namely, TClass > cmd-shift-N doesn't helps > > -- > Best regards, > Igor Stasenko. > -- Best regards, Igor Stasenko.

Dec. 3, 2013

how i can browse the users of some trait?

by Igor Stasenko

namely, TClass cmd-shift-N doesn't helps -- Best regards, Igor Stasenko.

Dec. 3, 2013

Re: [Pharo-dev] NativeBoost String Handling Bug?

by Igor Stasenko

Yes, when we discussed this with Martin (for a first time on that topic, i guess) all i wanted is a convenience method to _just_ make anonymous subclass.. how long this expression could be? it should be as long as: myClass createAnonymousSubclass. and what we have instead? First: self classBuilder anonymousSubclassOf: NBExternalArray. then newSubclass := AnonymousClassInstaller make: [ :builder | builder superclass: NBExternalArray ]. this is unacceptable. Because imagine one day you would want to port such code, (not necessary NB, but code which creates and uses anonymous subclasses), which code for porter, would be easier to understand how to port it if another dialect will miss any AnonymousClassInstaller? -- Best regards, Igor Stasenko.

Dec. 3, 2013

Building Pharo using Interpreter Class

by Kirstin Heidler

My freind Dimitri was not able to post his message. I am working with him on this. _______________________________________________________________________________ Hello, as part of a Seminar in the University im trying to build the PharoVM. According to the README file here ([1]) I was able to generate and to build the VM successfully. Now I would like to build the VM without Cog or Stack-to-Register optimizations... The problem here is, that I could not find any config class (which is a subclass of CPlatformConfig), that provides the right configurations and allows to build the VM without errors. I have tried to modify PharoUnixConfig(because it was the default config class), but unfortunately the build failes when the compiler tries to compile gcc3x-interp.c. Could somebody help me with this problem? How should I configure my own Config class? Basically our Group tries to implement an object table in Pharo and we want to use (and modify) the basic Interpreter class. [1] https://github.com/pharo-project/pharo-vm Best regards, Dimitri Korsch

Dec. 3, 2013

Re: [Pharo-dev] NativeBoost String Handling Bug?

by Esteban Lorenzano

I'm ok to add some convenient methods to class installers. just that I do not have time to do it right now, so be my guest :) Esteban On Tue, Dec 3, 2013 at 1:10 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > Yes > > "protocol: private" > anonymousSubclassInitElementType: aTypeName > "create and initialize the anonymous subclass of me" > > | newSubclass | > newSubclass := self classBuilder anonymousSubclassOf: NBExternalArray. > newSubclass initElementType: aTypeName. > ^ newSubclass > > > vs > > "protocol: private" > anonymousSubclassInitElementType: aTypeName > "create and initialize the anonymous subclass of me" > > | newSubclass | > newSubclass := AnonymousClassInstaller make: [ :builder | > "we're not using 'self' to avoid wrong subclassing from anonymous > subclass" > builder superclass: NBExternalArray ]. > newSubclass initElementType: aTypeName. > ^ newSubclass > > > And > > "protocol: class factory" > getClassForType: aTypeName > "Do not confuse.! This method answers an anonymous class, a subclass > of NBExternalTypeValue, > which can be used for instantiation later i.e: > > floatTypeClass := NBExternalTypeValue ofType: 'float'. > > float := floatTypeClass new. > float value: 1.5. > float value. > > " > > | newSubclass | > newSubclass := self classBuilder anonymousSubclassOf: > NBExternalTypeValue. > newSubclass valueType: aTypeName. > ^ newSubclass > > vs > > "protocol: class factory" > getClassForType: aTypeName > "Do not confuse.! This method answers an anonymous class, a subclass > of NBExternalTypeValue, > which can be used for instantiation later i.e: > > floatTypeClass := NBTypeValue ofType: 'float'. > > float := floatTypeClass new. > float value: 1.5. > float value. > > " > > | newSubclass | > newSubclass := AnonymousClassInstaller make: [ :builder | > "we're not using 'self' to avoid wrong subclassing from anonymous > subclass " > builder superclass: NBExternalTypeValue ]. > newSubclass initValueType: aTypeName. > ^ newSubclass > > > To anyone who changed this, can i have some canonical protocol for > creating anonymous subclasses > without referring to fuzzy , vague and unknown (as to me) > AnonymousClassInstaller > or other strange globals? > > > > On 3 December 2013 13:01, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com>wrote: > >> I testify, there are 2 conflicts >> >> Ben >> >> On 03 Dec 2013, at 12:44, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> apparently i was looking at wrong place, and according to report there's >> merge conflict. >> why? because i merged everything before commit. >> >> >> >> On 3 December 2013 12:09, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: >> >>> Igor >>> >>> where do you get this information? >>> Because I see >>> >>> https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/3549//artifact/vali… >>> and it is different. >>> >>> stef >>> >>> On Dec 3, 2013, at 11:59 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: >>> >>> i have no idea, but following is not related to what changes i did: >>> >>> ./pharo Pharo.image update --from-file=updates30.staged >>> >>> VersionnerProjectToolBar>>update (update is Undeclared) >>> >>> VersionnerProjectToolBar>>update (update is Undeclared) >>> >>> VersionnerProjectToolBar>>update (update is Undeclared) >>> >>> VersionnerProjectToolBar>>update (update is Undeclared) >>> >>> VersionnerProjectToolBar>>update (MBUpdateDevCommand is Undeclared) >>> >>> VersionnerProjectToolBar>>update (update is Undeclared) >>> >>> MBAddDescriptionCommandTest>>testExecute (MBAddDescriptionCommand is Undeclared) >>> >>> MBConfigurationInfoTest>>testInitialization (ConfigurationOfVersionner is Undeclared) >>> >>> MBAbstractVersionInfo>>cmdSetCurrentVersion (MBSetCurrentVersionCommand is Undeclared) >>> >>> MTProject>>addDependentProject:from:withVersion:loads:(repository is shadowed) >>> >>> >>> >>> >>> On 3 December 2013 10:17, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: >>> >>>> You know what? >>>> It will not be integrated because apparently the monkey tagged it as >>>> invalid. >>>> >>>> I have no idea why. I hate this automatic down grading. May be we >>>> should have a different tags to make the difference >>>> between >>>> >>>> work needed = nothing was done or something but it was never in >>>> the state where we could think it should be integrated >>>> was integration ready = it was ready but something happen >>>> >>>> Stef >>>> >>>> >>>> >>>> > Igor Stasenko wrote >>>> >> if yes then i think we can finally close the bug entry). >>>> > >>>> > I updated the issue and made your packages into a slice: >>>> > https://pharo.fogbugz.com/default.asp?7542 >>>> > SLICE-Issue-7542-NB-system-example-SeanDeNigris.1 >>>> > >>>> > >>>> > >>>> > ----- >>>> > Cheers, >>>> > Sean >>>> > -- >>>> > View this message in context: >>>> http://forum.world.st/NativeBoost-String-Handling-Bug-tp4726860p4726895.html >>>> > Sent from the Pharo Smalltalk Developers mailing list archive at >>>> Nabble.com <http://nabble.com/>. >>>> > >>>> >>>> >>>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >>> >>> >> >> >> -- >> Best regards, >> Igor Stasenko. >> >> >> > > > -- > Best regards, > Igor Stasenko. >

Dec. 3, 2013

Re: [Pharo-dev] NativeBoost String Handling Bug?

by Igor Stasenko

Yes "protocol: private" anonymousSubclassInitElementType: aTypeName "create and initialize the anonymous subclass of me" | newSubclass | newSubclass := self classBuilder anonymousSubclassOf: NBExternalArray. newSubclass initElementType: aTypeName. ^ newSubclass vs "protocol: private" anonymousSubclassInitElementType: aTypeName "create and initialize the anonymous subclass of me" | newSubclass | newSubclass := AnonymousClassInstaller make: [ :builder | "we're not using 'self' to avoid wrong subclassing from anonymous subclass" builder superclass: NBExternalArray ]. newSubclass initElementType: aTypeName. ^ newSubclass And "protocol: class factory" getClassForType: aTypeName "Do not confuse.! This method answers an anonymous class, a subclass of NBExternalTypeValue, which can be used for instantiation later i.e: floatTypeClass := NBExternalTypeValue ofType: 'float'. float := floatTypeClass new. float value: 1.5. float value. " | newSubclass | newSubclass := self classBuilder anonymousSubclassOf: NBExternalTypeValue. newSubclass valueType: aTypeName. ^ newSubclass vs "protocol: class factory" getClassForType: aTypeName "Do not confuse.! This method answers an anonymous class, a subclass of NBExternalTypeValue, which can be used for instantiation later i.e: floatTypeClass := NBTypeValue ofType: 'float'. float := floatTypeClass new. float value: 1.5. float value. " | newSubclass | newSubclass := AnonymousClassInstaller make: [ :builder | "we're not using 'self' to avoid wrong subclassing from anonymous subclass " builder superclass: NBExternalTypeValue ]. newSubclass initValueType: aTypeName. ^ newSubclass To anyone who changed this, can i have some canonical protocol for creating anonymous subclasses without referring to fuzzy , vague and unknown (as to me) AnonymousClassInstaller or other strange globals? On 3 December 2013 13:01, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com>wrote: > I testify, there are 2 conflicts > > Ben > > On 03 Dec 2013, at 12:44, Igor Stasenko <siguctua(a)gmail.com> wrote: > > apparently i was looking at wrong place, and according to report there's > merge conflict. > why? because i merged everything before commit. > > > > On 3 December 2013 12:09, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > >> Igor >> >> where do you get this information? >> Because I see >> >> https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/3549//artifact/vali… >> and it is different. >> >> stef >> >> On Dec 3, 2013, at 11:59 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> i have no idea, but following is not related to what changes i did: >> >> ./pharo Pharo.image update --from-file=updates30.staged >> >> VersionnerProjectToolBar>>update (update is Undeclared) >> >> VersionnerProjectToolBar>>update (update is Undeclared) >> >> VersionnerProjectToolBar>>update (update is Undeclared) >> >> VersionnerProjectToolBar>>update (update is Undeclared) >> >> VersionnerProjectToolBar>>update (MBUpdateDevCommand is Undeclared) >> >> VersionnerProjectToolBar>>update (update is Undeclared) >> >> MBAddDescriptionCommandTest>>testExecute (MBAddDescriptionCommand is Undeclared) >> >> MBConfigurationInfoTest>>testInitialization (ConfigurationOfVersionner is Undeclared) >> >> MBAbstractVersionInfo>>cmdSetCurrentVersion (MBSetCurrentVersionCommand is Undeclared) >> >> MTProject>>addDependentProject:from:withVersion:loads:(repository is shadowed) >> >> >> >> >> On 3 December 2013 10:17, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: >> >>> You know what? >>> It will not be integrated because apparently the monkey tagged it as >>> invalid. >>> >>> I have no idea why. I hate this automatic down grading. May be we should >>> have a different tags to make the difference >>> between >>> >>> work needed = nothing was done or something but it was never in >>> the state where we could think it should be integrated >>> was integration ready = it was ready but something happen >>> >>> Stef >>> >>> >>> >>> > Igor Stasenko wrote >>> >> if yes then i think we can finally close the bug entry). >>> > >>> > I updated the issue and made your packages into a slice: >>> > https://pharo.fogbugz.com/default.asp?7542 >>> > SLICE-Issue-7542-NB-system-example-SeanDeNigris.1 >>> > >>> > >>> > >>> > ----- >>> > Cheers, >>> > Sean >>> > -- >>> > View this message in context: >>> http://forum.world.st/NativeBoost-String-Handling-Bug-tp4726860p4726895.html >>> > Sent from the Pharo Smalltalk Developers mailing list archive at >>> Nabble.com <http://nabble.com/>. >>> > >>> >>> >>> >> >> >> -- >> Best regards, >> Igor Stasenko. >> >> >> > > > -- > Best regards, > Igor Stasenko. > > > -- Best regards, Igor Stasenko.

Dec. 3, 2013

Re: [Pharo-dev] Grease conflicts #packages with RPackage

by Stephan Eggermont

Stef wrote: >The real problem is that a CLASS now responds to the packages message. SUnitAPIDocumentation also implements packages class-side. If I try to add a instance side method #bla I get a debugger (but the method is added). Searching for implementors then also returns a debugger. I assume this problem wasnât seen as the classes implementing packages class-side donât have instance side behavior. The classes implementing packages class-side are SUnitAPIDocumentation AnnouncementsAPIDocumentation HelpAPIDocumentation ProfStefAPIHelp They all return an array of package name strings Stephan

Dec. 3, 2013

Re: [Pharo-dev] NativeBoost String Handling Bug?

by Benjamin

I testify, there are 2 conflicts Ben On 03 Dec 2013, at 12:44, Igor Stasenko <siguctua(a)gmail.com> wrote: > apparently i was looking at wrong place, and according to report there's merge conflict. > why? because i merged everything before commit. > > > > On 3 December 2013 12:09, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Igor > > where do you get this information? > Because I see > https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/3549//artifact/vali… > and it is different. > > stef > > On Dec 3, 2013, at 11:59 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> i have no idea, but following is not related to what changes i did: >> >> ./pharo Pharo.image update --from-file=updates30.staged >> >> VersionnerProjectToolBar>>update (update is Undeclared) >> >> VersionnerProjectToolBar>>update (update is Undeclared) >> >> VersionnerProjectToolBar>>update (update is Undeclared) >> >> VersionnerProjectToolBar>>update (update is Undeclared) >> >> VersionnerProjectToolBar>>update (MBUpdateDevCommand is Undeclared) >> >> VersionnerProjectToolBar>>update (update is Undeclared) >> >> MBAddDescriptionCommandTest>>testExecute (MBAddDescriptionCommand is Undeclared) >> >> MBConfigurationInfoTest>>testInitialization (ConfigurationOfVersionner is Undeclared) >> >> MBAbstractVersionInfo>>cmdSetCurrentVersion (MBSetCurrentVersionCommand is Undeclared) >> >> MTProject>>addDependentProject:from:withVersion:loads:(repository is shadowed) >> >> >> >> On 3 December 2013 10:17, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> You know what? >> It will not be integrated because apparently the monkey tagged it as invalid. >> >> I have no idea why. I hate this automatic down grading. May be we should have a different tags to make the difference >> between >> >> work needed = nothing was done or something but it was never in the state where we could think it should be integrated >> was integration ready = it was ready but something happen >> >> Stef >> >> >> >> > Igor Stasenko wrote >> >> if yes then i think we can finally close the bug entry). >> > >> > I updated the issue and made your packages into a slice: >> > https://pharo.fogbugz.com/default.asp?7542 >> > SLICE-Issue-7542-NB-system-example-SeanDeNigris.1 >> > >> > >> > >> > ----- >> > Cheers, >> > Sean >> > -- >> > View this message in context: http://forum.world.st/NativeBoost-String-Handling-Bug-tp4726860p4726895.html >> > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> > >> >> >> >> >> >> -- >> Best regards, >> Igor Stasenko. > > > > > -- > Best regards, > Igor Stasenko.

Dec. 3, 2013

Re: [Pharo-dev] Roassal 3d now support textures

by StÃ©phane Ducasse

did you move some functionality (to the place they belong) to NBOpenGL? Because this should be done and JB has already spent time on that. Stef > hi! > > Just to keep you up to date with the Roassal 3d effort. > https://www.facebook.com/photo.php?fbid=547995685287033&set=a.5299979037534… > > Cheers, > Alexandre > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > >

Dec. 3, 2013

Re: [Pharo-dev] NativeBoost String Handling Bug?

by Igor Stasenko

apparently i was looking at wrong place, and according to report there's merge conflict. why? because i merged everything before commit. On 3 December 2013 12:09, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > Igor > > where do you get this information? > Because I see > > https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/3549//artifact/vali… > and it is different. > > stef > > On Dec 3, 2013, at 11:59 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > i have no idea, but following is not related to what changes i did: > > ./pharo Pharo.image update --from-file=updates30.staged > > VersionnerProjectToolBar>>update (update is Undeclared) > > VersionnerProjectToolBar>>update (update is Undeclared) > > VersionnerProjectToolBar>>update (update is Undeclared) > > VersionnerProjectToolBar>>update (update is Undeclared) > > VersionnerProjectToolBar>>update (MBUpdateDevCommand is Undeclared) > > VersionnerProjectToolBar>>update (update is Undeclared) > > MBAddDescriptionCommandTest>>testExecute (MBAddDescriptionCommand is Undeclared) > > MBConfigurationInfoTest>>testInitialization (ConfigurationOfVersionner is Undeclared) > > MBAbstractVersionInfo>>cmdSetCurrentVersion (MBSetCurrentVersionCommand is Undeclared) > > MTProject>>addDependentProject:from:withVersion:loads:(repository is shadowed) > > > > > On 3 December 2013 10:17, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > >> You know what? >> It will not be integrated because apparently the monkey tagged it as >> invalid. >> >> I have no idea why. I hate this automatic down grading. May be we should >> have a different tags to make the difference >> between >> >> work needed = nothing was done or something but it was never in >> the state where we could think it should be integrated >> was integration ready = it was ready but something happen >> >> Stef >> >> >> >> > Igor Stasenko wrote >> >> if yes then i think we can finally close the bug entry). >> > >> > I updated the issue and made your packages into a slice: >> > https://pharo.fogbugz.com/default.asp?7542 >> > SLICE-Issue-7542-NB-system-example-SeanDeNigris.1 >> > >> > >> > >> > ----- >> > Cheers, >> > Sean >> > -- >> > View this message in context: >> http://forum.world.st/NativeBoost-String-Handling-Bug-tp4726860p4726895.html >> > Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> > >> >> >> > > > -- > Best regards, > Igor Stasenko. > > > -- Best regards, Igor Stasenko.

Dec. 3, 2013