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

Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers:

by stepharo

Just a remark. I think that we discarded the proposition of having aCol arithmetic sum but I found it nice because there if was clear that you want to get back 0 for #(). Stef

Dec. 24, 2015

Re: [Pharo-dev] Any thread-safe collection for Pharo?

by stepharo

there is AtomicQueue > > I want something more simple which not force me to remember what is > semaphore, monitor, mutex or whatever. Something like this: > > threadSafeCollection := AnyCollectionClass threadSafe. > > or > > threadSafeCollection := AnyCollectionInstance threadSafe. > > or more general > > threadSafeObject := AnyObjectInstance threadSafe > > > Thread safe wrappers should allow concurrent reads which blocked on > writes and writes which blocked on anything. > For example collection #add: method should wait until current #do: or > #add: completes. And #do: should wait until current #add: completes. I do not think that we have such behavior.

Dec. 24, 2015

Re: [Pharo-dev] Preview of new FFI?

by Pierce Ng

On Wed, Dec 23, 2015 at 08:00:31PM +0000, Esteban Lorenzano wrote: > as Torsten said, is in the image, and I cannot provide support until next > weekâ¦ Iâm counting the bytes here, to send mails :) but after that, of course > I will provide support, documentation (Iâm already working on it), etc. Thanks. I'll check it out. And thanks to Torsten for the comprehensive summary. Pierce

Dec. 24, 2015

Re: [Pharo-dev] Examples

by Torsten Bergmann

Dec. 23, 2015

Re: [Pharo-dev] Can I access symbolic constants from NB FFI?

by Eliot Miranda

Hi Mariano, > On Dec 22, 2015, at 8:36 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > >> On Tue, Dec 22, 2015 at 5:24 PM, tesonep(a)gmail.com <tesonep(a)gmail.com> wrote: >> Hello Mariano, >> WNOHANG is a constant is defined in sys/wait.h, after the compilation is not included in the object file. >> >> You will have to duplicate its value in the Smalltalk Code. It's value is 1, in linux is defined in bits/waitflags.h as >> >> #define WNOHANG 1 > > mmmmmm but then I would need to take care about its different values in different OS right? > I am reading for example this thread: https://groups.google.com/forum/#!topic/comp.lang.python/_5rCpfYR_ZE > > sunos 4.1.3 : #define WNOHANG 1 > Solaris 2.4 : #define WNOHANG 0100 > OSF1 2.0 : #define WNOHANG 0x1 > Ultrix 4.4 : #define WNOHANG 1 > irix 4.0.5C : #define WNOHANG 0x1 > irix 5.2 : #define WNOHANG 0100 > irix 6.0.1 : #define WNOHANG 0100 > Exactly. I've discussed this before. Please read http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2012-May/064382.… > OK..the thread is from 1995... I thought the POSIX standard would standardize that... > > I am now checking at /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/usr/include/sys/wait.h > > and it says: > #define WNOHANG 0x00000001 > > But again..I wonder how portable is to stick to that... > > Ok...maybe I will need to go with a VM primitive as #primGetChildExitStatus: that way I can do the: > > self cCode: 'waitpid ( pidToHandle, &exitStatus, WNOHANG )' inSmalltalk: [ exitStatus := -1 ]. > > > pd: que groso Pablito verte por aca!!!! > >> Cheers, >> Pablo >> >>> On Tue, Dec 22, 2015 at 5:12 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >>> Hi guys, >>> >>> Say I want to call to waitpid like this: >>> >>> waitpid(childID, &status, WNOHANG); >>> >>> How can I do since I don't have access to WNOHANG int value in order to send it via argument .... ??? >>> >>> Any idea? >>> >>> Thanks in advance, >>> >>> Mariano >>> http://marianopeck.wordpress.com >> >> Pablo Tesone. >> tesonep(a)gmail.com > > Mariano > http://marianopeck.wordpress.com _,,,^..^,,,_ (phone)

Dec. 23, 2015

Re: [Pharo-dev] Examples

by Peter UhnÃ¡k

The problem with instance-side examples is that you need an instance to work with (otherwise there is not much point of having it on the instance-side), unless there would be pragma for it... e.g. MyObject>>myInstanceSideExample <rtExample: 'self new myInstanceSideExample open'> |v| v := RTView new. ... ^ v The architecture for Nautilus icons is very easy to change or extend, look at AbstractMethodIconAction and it's subclasses. You could even easily add your own class specifically for Roassal examples (and bundle it with Roassal) e.g. something like this (this is just an idea; I haven't tried running the code...) RTMethodIsRoassalExample>>isActionHandled ^ method methodClass className beginsWith: 'RT' and: [ method selector includesSubstring: 'example' caseSensitive: false ]. RTMethodIsRoassalExample>>privateActionIcon ^ IconicButton actionSelector: #runExample; etc... RTMethodIsRoassalExample>>runExample ^ (method methodClass new perform: method) open "assuming the method returns RTView instance..." Peter On Wed, Dec 23, 2015 at 10:33 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > Having examples on the class sides imply that examples are not apparent when > I do not select the class side of a class. > And this is a pityâ¦ > > Maybe a particular icon can designate classes with examples? > Or what about making the <script> pragma works also for instance methods and > not only class methods? > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > >

Dec. 23, 2015

Dealing with Class and Metaclass instances when using STON

by Sven Van Caekenberghe

Hi, In STON #bleedingEdge I added the ability to write and read Class and Metaclass instances by using their global name. So, Point will be written as Class[#Point] while Point class will be written as Metaclass[#Point]. This is of course a short-circuit solution for the complex structure that a class actually is, but a reasonable compromise. It is in any case better than not handling these types of instances, which was the case before. === Name: STON-Core-SvenVanCaekenberghe.64 Author: SvenVanCaekenberghe Time: 23 December 2015, 10:50:14.195912 pm UUID: b7ced20a-a7a4-4b0f-8f27-db73231eeecb Ancestors: STON-Core-SvenVanCaekenberghe.63 Added the ability to write and read Class and Metaclass instances using their global name === Name: STON-Tests-SvenVanCaekenberghe.59 Author: SvenVanCaekenberghe Time: 23 December 2015, 10:51:06.830762 pm UUID: 9f684bc1-45e1-4bfa-885b-c56ea178bfca Ancestors: STON-Tests-SvenVanCaekenberghe.58 Added unit test for the ability to write and read Class and Metaclass instances using their global name === Thanks to Norbert Hartl for requesting the feature and for test driving it. Sven

Dec. 23, 2015

Examples

by Alexandre Bergel

Hi! Having examples on the class sides imply that examples are not apparent when I do not select the class side of a class. And this is a pityâ¦ Maybe a particular icon can designate classes with examples? Or what about making the <script> pragma works also for instance methods and not only class methods? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 23, 2015

Re: [Pharo-dev] Preview of new FFI?

by Esteban Lorenzano

Hi, This is a good summary, thanks Torsten! Some notes between lines: > On 23 Dec 2015, at 13:30, Torsten Bergmann <astares(a)gmx.de> wrote: > > I guess Esteban is busy as he is with Stef in Togo. I started porting to > new FFI initial stuff and chatted with Esteban on Slack. > > When you use the latest Pharo 5 image (together with the spur VM) you > have the new FFI right inside. Athens is running already on the new FFI. > > NB is still not unloaded - but it will be unloaded soon. The idea is that > people can recover what they need afterwards. For some cases it should be > straightforward to convert. > > A short summary of my findings: > > - check the "FFI-NB" package in recent Pharo 5 images like Pharo 5 #50510 as of today > The name is misleading - it is not the NativeBoost but the new FFI > - check the new classes in this package that are prefixed with "FFI" like > FFIExternalObject (replacement for NBExternalObject), FFIExternalStructure > (replacement for NBExternalStructure), ... > - If you generate fields from a struct the accessors are not generated > into non-package "*generated-code-non-existing-package" but are now generated into > method category "accessing structure variables" and will therefore be part of your > MCZ code package yes, you can rewrite the class side method #generatedFieldProtocolName if you still want an special protocol, but I do not see the need for it. > - #nbCall: and #nbCall:module: work for compatibility, I guess we should add a deprecation > to them yes, but that would mean I need to rewrite half of athens to change the methods so I preferred to let it like that for now :) I suppose a path like: transparent in pharo 5, deprecated in pharo 6 and non-exiting in pharo 7 is a good estimation to allow people (and me) to do all the changes. Is not a complicated task, of courseâ¦ but needs to be done :) > - it is better to use ffiCall:, ffiCall:module: now yes, it is. > - there is no need to have a pragma with NativeBoostPlugin anymore, at least it > worked for me without it just by using #ffiCall: â¦ indeed :) > - there is a new repo: http://smalltalkhub.com/#!/~Pharo/FFI-NB <http://smalltalkhub.com/#!/~Pharo/FFI-NB> since last week, > but I guess the code in the image is more recent mmmâ¦ it should be in sync, but I might be wrong. In that case, if someone can sync it, it will be cool. > > Problems I've experienced so far while trying to port my OS-Windows project: > - FIICallout does not understand #optionAt:, no support for options like #WinUnicode so far no idea how to implement that, I will check it when Iâm back. Of course, it was previewed some functionality was going to be missing, but the idea is to add them as people report it. > - FFIExternalType sizeOf: #ulong failed yes, I forgot to implement it. But in any case, that will be replaced by an âin imageâ approach so use it wisely :) > - the spur VM for Windows does not include all latest fixes for Windows VM, like > CTRL keys (https://pharo.fogbugz.com/f/cases/17289 <https://pharo.fogbugz.com/f/cases/17289>) not FFI related, Iâm aware of thisâ¦ is just that I need time to merge latest 3 to 6 months changes in the VM to spur branch. > > Hope this helps a little bit until some more bugs are sorted out/a more detailed info > for conversion is available. yes, Iâm working on documentationâ¦ but as always is not so easyâ¦ hopefully in next couple of weeks will be ready. cheers, Esteban > > Bye > T. > > Gesendet: Mittwoch, 23. Dezember 2015 um 13:55 Uhr > Von: "Mariano Martinez Peck" <marianopeck(a)gmail.com <mailto:marianopeck@gmail.com>> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org>> > Betreff: Re: [Pharo-dev] Preview of new FFI? > > We are in the same boat. Even worst, I suspect I am using some parts of ASMJIT which I guess won't be in new FFI, so I have on clue how I would make that parts to work.... > > On Wed, Dec 23, 2015 at 9:16 AM, Pierce Ng <pierce(a)samadhiweb.com> wrote:Hi, > > (For Esteban perhaps...) > > Is there an image/VM combo to preview the new FFI? I just made NBSQLite3 work > with SQLcipher (for transparent database encryption) but don't want to spend > any effort refactoring if I need to redo for the new FFI. > > Pierce > > -- > Mariano > http://marianopeck.wordpress.com[http://marianopeck.wordpress.com] <http://marianopeck.wordpress.com[http://marianopeck.wordpress.com]>

Dec. 23, 2015

Re: [Pharo-dev] Preview of new FFI?

by Esteban Lorenzano

if you are using *anything* of ASMJIT, nit just pars, you are in problems :) it will be removed as the VM does not support it by default anymore. now, if your âparts of ASMJITâ means you are doing nbCall:module:, structs, arrays, etcâ¦. then you are ok. (But if I would be you, I would be working on Pharo 5.0 since what we are asking you is for running there, not in Pharo 4). Of course, âyou are okâ but you will need to tweak some things here and there. Esteban > On 23 Dec 2015, at 12:55, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > We are in the same boat. Even worst, I suspect I am using some parts of ASMJIT which I guess won't be in new FFI, so I have on clue how I would make that parts to work.... > > On Wed, Dec 23, 2015 at 9:16 AM, Pierce Ng <pierce(a)samadhiweb.com <mailto:pierce@samadhiweb.com>> wrote: > Hi, > > (For Esteban perhaps...) > > Is there an image/VM combo to preview the new FFI? I just made NBSQLite3 work > with SQLcipher (for transparent database encryption) but don't want to spend > any effort refactoring if I need to redo for the new FFI. > > Pierce > > > > > -- > Mariano > http://marianopeck.wordpress.com <http://marianopeck.wordpress.com/>

Dec. 23, 2015