February 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Spotter suggestion

by Peter UhnÃ¡k

Or have a shortcut that when held down will show the shortcuts. :) On Thu, Feb 18, 2016 at 1:31 PM, Guille Polito <guillermopolito(a)gmail.com> wrote: > Yeap, but it kind of kills the workflow... Why showing the shortcut in the > tool is not an option? > > > On 02/18/2016 01:18 PM, Tudor Girba wrote: > >> Hi, >> >> Spotter from the latest Pharo has a help button with shortcuts explained. >> >> Cheers, >> Doru >> >> >> On Feb 18, 2016, at 12:14 PM, Guille Polito <guillermopolito(a)gmail.com> >>> wrote: >>> >>> Hi Doru et al! >>> >>> I was here having difficulties to see how to use spotter, and how to >>> dive into, and show more results, because the shortcuts are hidden if you >>> don't know them by heart. >>> >>> So I thought, why the spotter ui does not >>> - propose the shortcuts to dive at the right of the list? >>> - propose some extra items for e.g., show all items? >>> >>> Something like the attached picture... >>> >>> What do you think? >>> >>> Guille >>> <spotter.png> >>> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Not knowing how to do something is not an argument for how it cannot be >> done." >> >> >> > >

Feb. 18, 2016

Re: [Pharo-dev] FogBugz (Case [Issue]17625) Kernel - The immediateSubclass... and variableSubclass method need comments

by Alexandre Bergel

Marcus, you are a rocket. Thank you! Alexandre > On Feb 18, 2016, at 6:39 AM, Pharo Issue Tracker <do-not-reply(a)pharo.fogbugz.com> wrote: > > > Ulysse The Galactic Monkey From Outer Spaceresolved Case 17625: The immediateSubclass... and variableSubclass method need comments and assigned it to you: > > Bug in Kernel: 1. Pharo Image > > In 50588 > > Status changed: > Resolved (Fix To Include) Resolved (Fix Integrated) > > Priority: 5 â Fix If Time Status: Resolved (Fix Integrated) > Assigned to: Alexandre Bergel Milestone: Pharo5.0 > > > Go to Case > > Don't want FogBugz notifications anymore? Update your preferences. > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 18, 2016

Re: [Pharo-dev] Spotter suggestion

by Guille Polito

Yeap, but it kind of kills the workflow... Why showing the shortcut in the tool is not an option? On 02/18/2016 01:18 PM, Tudor Girba wrote: > Hi, > > Spotter from the latest Pharo has a help button with shortcuts explained. > > Cheers, > Doru > > >> On Feb 18, 2016, at 12:14 PM, Guille Polito <guillermopolito(a)gmail.com> wrote: >> >> Hi Doru et al! >> >> I was here having difficulties to see how to use spotter, and how to dive into, and show more results, because the shortcuts are hidden if you don't know them by heart. >> >> So I thought, why the spotter ui does not >> - propose the shortcuts to dive at the right of the list? >> - propose some extra items for e.g., show all items? >> >> Something like the attached picture... >> >> What do you think? >> >> Guille >> <spotter.png> > -- > www.tudorgirba.com > www.feenk.com > > "Not knowing how to do something is not an argument for how it cannot be done." > >

Feb. 18, 2016

Re: [Pharo-dev] Spotter suggestion

by Tudor Girba

Hi, Spotter from the latest Pharo has a help button with shortcuts explained. Cheers, Doru > On Feb 18, 2016, at 12:14 PM, Guille Polito <guillermopolito(a)gmail.com> wrote: > > Hi Doru et al! > > I was here having difficulties to see how to use spotter, and how to dive into, and show more results, because the shortcuts are hidden if you don't know them by heart. > > So I thought, why the spotter ui does not > - propose the shortcuts to dive at the right of the list? > - propose some extra items for e.g., show all items? > > Something like the attached picture... > > What do you think? > > Guille > <spotter.png> -- www.tudorgirba.com www.feenk.com "Not knowing how to do something is not an argument for how it cannot be done."

Feb. 18, 2016

Spotter suggestion

by Guille Polito

Hi Doru et al! I was here having difficulties to see how to use spotter, and how to dive into, and show more results, because the shortcuts are hidden if you don't know them by heart. So I thought, why the spotter ui does not - propose the shortcuts to dive at the right of the list? - propose some extra items for e.g., show all items? Something like the attached picture... What do you think? Guille

Feb. 18, 2016

Re: [Pharo-dev] FFI BoxedFloat64 bug?

by Esteban Lorenzano

> On 17 Feb 2016, at 19:35, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > >> I don't understand. All BoxedFloat have 8 bytes, that's why they are called BoxedFloat64. There are no 4-bytes floats in Pharo. Even in 32 bits. > > I have some code that involve FFI and floats that was working before Spur. > I got the error mentioned by Alex. > Defining this pointer method gives a weird behavior. > > It would be great to have this fixed. probably because of what I just describedâ¦ I will commit a fix. > > Alexandre > >> >> 2016-02-12 18:06 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >>> On 12 Feb 2016, at 17:50, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: >>> >>> On Fri, Feb 12, 2016 at 5:45 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> Float>>#pointer >>> ^ (ByteArray new: FFIExternalType pointerSize) >>> floatAt: 1 put: self; >>> yourself >>> >>> Yes it does the trick :) Thanks! >> >> yes and no (I made a mistake): that works because incidentally pointers and floats have same size (4 bytes)â¦ but can happen that it is not (doubles have 8 bytes)â¦ but is ok for now :) >> I will fix it correctly next week. >> >> Esteban >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

Feb. 18, 2016

Re: [Pharo-dev] FFI BoxedFloat64 bug?

by Esteban Lorenzano

but in C (32bits) floats are 4 bytes, so when you do: ByteArray new floatAt: 1 put: somePharoFloat; it will cast it to 4 bytes (if it fits which is most of the cases). but as I saidâ¦ it is an error I need to fix :) Esteban > On 12 Feb 2016, at 20:50, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > I don't understand. All BoxedFloat have 8 bytes, that's why they are called BoxedFloat64. There are no 4-bytes floats in Pharo. Even in 32 bits. > > 2016-02-12 18:06 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > >> On 12 Feb 2016, at 17:50, Aliaksei Syrel <alex.syrel(a)gmail.com <mailto:alex.syrel@gmail.com>> wrote: >> >> On Fri, Feb 12, 2016 at 5:45 PM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >> Float>>#pointer >> ^ (ByteArray new: FFIExternalType pointerSize) >> floatAt: 1 put: self; >> yourself >> >> Yes it does the trick :) Thanks! > > yes and no (I made a mistake): that works because incidentally pointers and floats have same size (4 bytes)â¦ but can happen that it is not (doubles have 8 bytes)â¦ but is ok for now :) > I will fix it correctly next week. > > Esteban >

Feb. 18, 2016

Re: [Pharo-dev] Object>>rollToArity:?

by Esteban Lorenzano

Iâm not happy with the method name, but I think is well explained in method comments: ExternalAddress>>rollToArity: arity "This will 'roll' a pointer to a certain arity. What does this means? Let's say I have a method who will be called with a ** arity: method: aPointer self ffiCall: #( method ( MyExternalObjectClass **aPointer) ) This usually means that method will put a pointer in the address of aPointer. And what I actually want is this pointer. So I do Something like this: p := MyExternalObjectClass new. self mehod: p. And I expect to have 'p' correctly initialised on return. Well... tha's not so simple :) When compiling #method:, UnifiedFFI needs to first 'roll' the pointer (which means to take a pointer of a pointer of a pointer... as many pointers as arity solicited), and then, after call, it needs to 'unroll' all this pointers (see #unrollFromArity: method) â ByteArray>>rollToArity: arity "This is complicated... I assuming this ways of calling a function: arity == 1: ----------- ByteArray works as pointer buffer of single pointer to something: ex 1) buffer := ByteArray new: 4. self ffiCall: #( void function (int *buffer) ). ex 2) buffer := 'Hello, World' asByteArray. self ffiCall: #( void function (char *buffer) ). arity > 1: ---------- ByteArray works as pointer to allocate results: ex 1) pointer := ByteArray new: (FFIExternalType pointerSize). self ffiCall: #( void function ( char **answer )). In this case this will not work fine because content of ByteArray needs to be a pointer too, and then it needs to be allocated in the heap... while this could be managed, I'm puting for the moment just an error and a recommendation of using an ExternalAddress. " basically, is the equivalent of â&â operator in C. you can manually do the same by doing: | var | var := 42 pointer. who will give you a byte array with signedLongAt: 1 == 42. â¦ but since old NB was doing this implicitly, we need to provide it too :) Esteban ps: Why do you need to know it? This is internal in UnifiedFFI so nobody should need to deal with it. > On 17 Feb 2016, at 16:49, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Esteban, > > What Object>>rollToArity: is supposed to do? It belongs to UnifiedFFI > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

Feb. 18, 2016

How was BoxedFloat64 integrated into the image ?

by Nicolai Hess

Because we have compiled methods with BoxedFloat64 associations in the methods literals, but the source code still shows only "Float". 17638 <https://pharo.fogbugz.com/f/cases/17638/Browsing-calls-on-BoxedFloat64-show…> Browsing calls on BoxedFloat64 shows methods with reference to BoxedFloat64 in the code

Feb. 18, 2016

Stabilization Slack Channel

by Guille Polito

Hi! With Esteban we set up a new slack channel to discuss about the stabilization of Pharo5. The idea is to discuss stabilization problems in a quicker way than the issue tracker (which we should also use btw:)). The description of the channel is Temporary channel to work on urgent stabilisation issues. Everybody willing to help is invited to join :) Guille

Feb. 18, 2016