- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] New Cog VMs available

by Eliot Miranda

On Fri, Nov 21, 2014 at 4:08 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > ... at http://www.mirandabanda.org/files/Cog/VM/VM.r3144. > > Apologies; the 3143 VMs were broken. > and I'm sorry to say the 3144 look broken too. I suspect the VM is not correctly normalizing bit-operations on large integers into SmallIntegers as expected. > CogVM binaries as per VMMaker.oscog-eem.950/r3144 > > Fix regression in new primitiveBitShift. > Introduce >>> as an explicitly signed shift. > 64-bit ize magnitude64BitIntegerFor:neg:, > positive64BitIntegerFor: & signed64BitIntegerFor: > -- > best, > Eliot > -- best, Eliot

Nov. 22, 2014

Re: [Pharo-dev] Listening for shift key pressed

by Ben Coman

Aliaksei Syrel wrote: > Hi, Nicolai > > Thanks for suggestion. I'm using Mac 10.10 and it doesn't show any > notifications for shift.. > I'll open an issue for this. > > Cheers, > Alex I confirm this works in Windows, but not on OSX. cheers -ben > > On Fri, Nov 21, 2014 at 10:20 PM, Nicolai Hess <nicolaihess(a)web.de > <mailto:nicolaihess@web.de>> wrote: > > If you look at KeyPrinterMorph you'll see that it indeed handles a > single shift key down. > > 2014-11-21 17:36 GMT+01:00 Aliaksei Syrel <alex.syrel(a)gmail.com > <mailto:alex.syrel@gmail.com>>: > > Hi Ben, > > If at the end of InputEventFetcher>>__waitForInput > you put "Transcript crShow: Time now" > and I think you'll be looking at as raw an event aas you can > get. > > > Now this exhibits some strange behaviour? Pushing <shift> > on its own does not produce an event, however pushing > <shift> fast multiple times does generate events. ??? > > It's maybe because you move mouse, or randomly touch touchpad. > > After some investigations and digging lower and lower till > primitive methods, I realized that VM itself doesn't queue an > event after user presses Shift. It's just a modifier bit, that > is applied on a real events, such as mouse moves or normal > keyboard events. > > Cheers, > Alex > > > >

Nov. 22, 2014

New Cog VMs available

by Eliot Miranda

... at http://www.mirandabanda.org/files/Cog/VM/VM.r3144. Apologies; the 3143 VMs were broken. CogVM binaries as per VMMaker.oscog-eem.950/r3144 Fix regression in new primitiveBitShift. Introduce >>> as an explicitly signed shift. 64-bit ize magnitude64BitIntegerFor:neg:, positive64BitIntegerFor: & signed64BitIntegerFor: -- best, Eliot

Nov. 22, 2014

Re: [Pharo-dev] Listening for shift key pressed

by Nicolai Hess

Ok, I tested this with windows and linux only. nicolai 2014-11-21 23:06 GMT+01:00 Aliaksei Syrel <alex.syrel(a)gmail.com>: > Hi, Nicolai > > Thanks for suggestion. I'm using Mac 10.10 and it doesn't show any > notifications for shift.. > I'll open an issue for this. > > Cheers, > Alex > > On Fri, Nov 21, 2014 at 10:20 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> If you look at KeyPrinterMorph you'll see that it indeed handles a single >> shift key down. >> >> 2014-11-21 17:36 GMT+01:00 Aliaksei Syrel <alex.syrel(a)gmail.com>: >> >>> Hi Ben, >>> >>> If at the end of InputEventFetcher>>waitForInput >>>> you put "Transcript crShow: Time now" >>>> and I think you'll be looking at as raw an event aas you can get. >>> >>> >>> Now this exhibits some strange behaviour? Pushing <shift> on its own >>>> does not produce an event, however pushing <shift> fast multiple times does >>>> generate events. ??? >>> >>> It's maybe because you move mouse, or randomly touch touchpad. >>> >>> After some investigations and digging lower and lower till primitive >>> methods, I realized that VM itself doesn't queue an event after user >>> presses Shift. It's just a modifier bit, that is applied on a real events, >>> such as mouse moves or normal keyboard events. >>> >>> Cheers, >>> Alex >>> >>> >> >> >

Nov. 21, 2014

Re: [Pharo-dev] Listening for shift key pressed

by Aliaksei Syrel

Hi Stef, cool, looking forward to seeing it works :) Because we really need shift event Cheers, Alex On Fri, Nov 21, 2014 at 11:13 PM, stepharo <stepharo(a)free.fr> wrote: > Hi alex > > the way these low level events are managed sucks. This is why we started > to reify them. Now with OSWindow (we should review the code) > and I hope it will get better. Also the VM was not generating event for > shift and I hope that OSwindow will support that :) > Le 21/11/14 17:36, Aliaksei Syrel a Ã©crit : > > Hi Ben, > > If at the end of InputEventFetcher>>waitForInput >> you put "Transcript crShow: Time now" >> and I think you'll be looking at as raw an event aas you can get. > > > Now this exhibits some strange behaviour? Pushing <shift> on its own >> does not produce an event, however pushing <shift> fast multiple times does >> generate events. ??? > > It's maybe because you move mouse, or randomly touch touchpad. > > After some investigations and digging lower and lower till primitive > methods, I realized that VM itself doesn't queue an event after user > presses Shift. It's just a modifier bit, that is applied on a real events, > such as mouse moves or normal keyboard events. > > Cheers, > Alex > > > >

Nov. 21, 2014

Re: [Pharo-dev] Listening for shift key pressed

by stepharo

Hi alex the way these low level events are managed sucks. This is why we started to reify them. Now with OSWindow (we should review the code) and I hope it will get better. Also the VM was not generating event for shift and I hope that OSwindow will support that :) Le 21/11/14 17:36, Aliaksei Syrel a Ã©crit : > Hi Ben, > > If at the end of InputEventFetcher>>waitForInput > you put "Transcript crShow: Time now" > and I think you'll be looking at as raw an event aas you can get. > > > Now this exhibits some strange behaviour? Pushing <shift> on its > own does not produce an event, however pushing <shift> fast > multiple times does generate events. ??? > > It's maybe because you move mouse, or randomly touch touchpad. > > After some investigations and digging lower and lower till primitive > methods, I realized that VM itself doesn't queue an event after user > presses Shift. It's just a modifier bit, that is applied on a real > events, such as mouse moves or normal keyboard events. > > Cheers, > Alex

Nov. 21, 2014

Re: [Pharo-dev] Listening for shift key pressed

by Aliaksei Syrel

Hi, Nicolai Thanks for suggestion. I'm using Mac 10.10 and it doesn't show any notifications for shift.. I'll open an issue for this. Cheers, Alex On Fri, Nov 21, 2014 at 10:20 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > If you look at KeyPrinterMorph you'll see that it indeed handles a single > shift key down. > > 2014-11-21 17:36 GMT+01:00 Aliaksei Syrel <alex.syrel(a)gmail.com>: > >> Hi Ben, >> >> If at the end of InputEventFetcher>>waitForInput >>> you put "Transcript crShow: Time now" >>> and I think you'll be looking at as raw an event aas you can get. >> >> >> Now this exhibits some strange behaviour? Pushing <shift> on its own >>> does not produce an event, however pushing <shift> fast multiple times does >>> generate events. ??? >> >> It's maybe because you move mouse, or randomly touch touchpad. >> >> After some investigations and digging lower and lower till primitive >> methods, I realized that VM itself doesn't queue an event after user >> presses Shift. It's just a modifier bit, that is applied on a real events, >> such as mouse moves or normal keyboard events. >> >> Cheers, >> Alex >> >> > >

Nov. 21, 2014

Re: [Pharo-dev] Listening for shift key pressed

by Nicolai Hess

If you look at KeyPrinterMorph you'll see that it indeed handles a single shift key down. 2014-11-21 17:36 GMT+01:00 Aliaksei Syrel <alex.syrel(a)gmail.com>: > Hi Ben, > > If at the end of InputEventFetcher>>waitForInput >> you put "Transcript crShow: Time now" >> and I think you'll be looking at as raw an event aas you can get. > > > Now this exhibits some strange behaviour? Pushing <shift> on its own does >> not produce an event, however pushing <shift> fast multiple times does >> generate events. ??? > > It's maybe because you move mouse, or randomly touch touchpad. > > After some investigations and digging lower and lower till primitive > methods, I realized that VM itself doesn't queue an event after user > presses Shift. It's just a modifier bit, that is applied on a real events, > such as mouse moves or normal keyboard events. > > Cheers, > Alex > >

Nov. 21, 2014

Re: [Pharo-dev] [Vm-dev] Re: [squeak-dev] Float hierarchy for 64-bit Spur

by Chris Muller

> I have always felt that the mapping of Float to 64-bit double and FloatArray > to 32-bit float is awkward. It may be that 32-bit floats are becoming less > relevant nowadays, but if short float values are still important, then it >From the sense that a lot of computing is addressing fuzzy pattern matching, 32-bit speed and space are actually becoming more relevant. > would be nice to be able to represent them directly. I like the idea of having > a Float class and a Double class to represent the two most common representations. > A class hierarchy that could potentially support this sounds like a good idea to me. > > I have no experience with VW, but a LimitedPrecisionReal hierachy sounds like a > reasonable approach. > > Dave >

Nov. 21, 2014

Re: [Pharo-dev] Float hierarchy for 64-bit Spur

by stepharo

Le 21/11/14 02:51, Eliot Miranda a Ã©crit : > Hi All, > > 64-bit Spur can usefully provide an immediate float, a 61-bit > subset of the ieee double precision float. The scheme steals bits > from the mantissa to use for the immediate's 3-bit tag pattern. So > values have the same precision as ieee doubles, but can only represent > the subset with exponents between 10^-38 and 10^38, the > single-precision range. The issue here is how to organize the class > hierarchy. > > The approach that looks best to me is to modify class Float to be an > abstract class, and add two subclasses, BoxedFloat and SmallFloat, > such that existing boxed instances of Float outside the SmallFloat > range will become instances of BoxedFloat and instances within that > range will be replaced by references to the relevant SmallFloat. > > With this approach ... > > - Float pi etc can still be used, even though they will answer > instances of SmallFloat. But tests such as "self assert: result class > == Float." will need to be rewritten to e.g. "self assert: result > isFloat". > > - BoxedFloat and SmallFloat will not be mentioned much at all since > floats print themselves literally, and so the fact that the classes > have changed won't be obvious. > > - the boxed Float primitives (receiver is a boxed float) live in > BoxedFloat and the immediate ones live in SmallFloat. Making > SmallFloat a subclass of Float poses problems for all the primitives > that do a super send to retry, since the boxed Float prims will be > above the unboxed ones and so the boxed ones would have to test for an > immediate receiver. > > > An alternative, that VW took (because it has both Float and Double) is > to add a superclass, e.g. LimitedPrecisionReal, move most of the > methods into it, and keep Float as Float, and add SmallFloat as a > subclass of LimitedPrecisionReal. Then while class-side methods such > as pi would likely be implemented in LimitedPrecisionReal class, sends > to Float to access them find them via inheritance. An automatic > reorganization which moves only primitives out of LimitedPrecisionReal > is easy to write. Eliot the solution proposed by VM is nice in the sense that we can continue to use Float pi... On the other hand, I like the design used on objective-c when the superclass act as a factory for its subclass hidding concrete implementation classes. Now I do not know if his would make sense for Float. Another point, I do not really like Boxed because this is the first time we use it. May be SmallFloat would be in the same spirit than SmallInteger. > > Thoughts? > -- > best, > Eliot

Nov. 21, 2014