- Pharo-dev - lists.pharo.org

VM fixes to review

by Ben Coman

I notice several VM fixes [1] submitted by Nicolas 6 months ago. They are categorized as Milestone=Later, so I'm bumping them here just in case these slipped through the cracks to get them into Pharo 4. [1] https://pharo.fogbugz.com/default.asp?pgx=LF&ixFilter=36 But then I think I remember that early in Pharo 4 cycle, the Pharo VM was aligned more closely with with Eliot's - so maybe some of these are already included? cheers -ben

Nov. 16, 2014

Re: [Pharo-dev] Julia vs Pharo

by Alexandre Bergel

Hi Serge! Thanks for sharing this. I indeed believe that scientific computing will play a big role in Pharo adoption by a large public Alexandre > On Nov 15, 2014, at 2:57 PM, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > > Hi all, > > I find a recent paper about Julia that might be appealing for people > interested in doing scientific computation in Pharo (like the > SciSmalltalk community) : http://arxiv.org/pdf/1411.1607v1.pdf > "Julia: A fresh approach to numerical computing" > > Julia is a new dynamic programming language for scientific programming > with much higher performance than R or Python. > > I found that some concepts are quite closed to Pharo in fact: > > - meta-programming and code generation > - arbitrary precision integer > - JIT compiler (based on LLVM) > - call to C API > > What is missing in Pharo at the moment: > - multiple dispatch > - arbitrary precision float > - dynamic dataflow type inference > - optional type annotations (maybe with pluggable type extensions for Pharo ?) > - special matrices types like spares or dense matrix, tri-diagonal, etc ... > - vectorization > > Regards, > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Help fight Ebola by joining the Computing for Ebola Challenge > http://bit.ly/1oEdBag > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 16, 2014

Re: [Pharo-dev] [NB] Undocumented NativeBoost options

by Max Leske

> On 15.11.2014, at 20:53, stepharo <stepharo(a)free.fr> wrote: > > > On 15/11/14 12:37, Max Leske wrote: >> I got a bit frustrated and ended up searching the source for â[\w]opt[[:upper]]â to find all NativeBoost options. Some of those options are in fact undocumented: >> >> optMayGC >> optProxyLabels >> optCdecl >> optReturnNullAsNil >> optStdcall >> optNonMovable >> optReserveCallgateSpace >> optDebug >> optNoAlignment >> optEmitCall >> optNoCleanup >> optCheckFailOnEveryArgument >> optStringOrNull >> WinUnicode >> >> NBFFICallout>>defaultOptions documents most options but refers to NBFFICallout>>allOptions, wich does not exist. Most of the above options can be considered internal, I guess, but the one option I needed (âoptStringOrNullâ) isnât documented anywhere. I had to step through the execution to find out why my function call wasnât working (because I was trying to use âoptCoerceNilToNullâ and didnât know that strings need a special option). >> >> Iâd be very thankful if these options would be included in the documentation. > Which documentation? There is one? Well, thereâs a bit of documentation on Google code and then thereâs NBFFICallout class>>defaultOptions, which has some comments. Thatâs it basically. > And yes this pisses me off. > >> >> Note: âWinUnicodeâ is used by the Windows code in a couple of places, even though the option name is not valid, according to NBNativeCodeGen>>parseOptions: >> >> Cheers, >> Max >> > >

Nov. 15, 2014

Re: [Pharo-dev] Configurations and Github for a specialised configuration browswe

by kilon alios

yes I was thinking about git tags too, but since I have never tried this with pharo or other smalltalk I had my concerns how well it would work. I am really glad it works for you, that means it will works for me as well if I want some versioning for users. I also like the github url very much, simple concise and direct to the point. Thanks for the link too, I am reading it now. On Sun, Nov 16, 2014 at 12:03 AM, Dale Henrichs < dale.henrichs(a)gemtalksystems.com> wrote: > > > On Sat, Nov 15, 2014 at 9:54 AM, kilon alios <kilon.alios(a)gmail.com> > wrote: > >> Travis seems like an overkill for me right now. Sure if I was bombarded >> by pull requests from other developers but in reality I work alone . But I >> will definitely keep it in mind in case my projects become so popular that >> people start to send me pull requests regularly. >> > > Makes sense. > > >> >> All I wanted was an easy way to install code from github to pharo without >> the need to install git and you gave me that. Next step is to see how I >> would integrate github with pharo better, should I use Configuration >> versions or is it better to use branches ? I am more orientated towards >> branches. >> > > With git I think that configurations are really no longer necessary ... I > prefer to use branches to isolate development work from the master branch > (topic branches) and then use tags to identify release points ... with > travis-ci validating the commits, I can do continuous deployment on the > master branch ... For Seaside31 we are using tags to stay in sync with the > mcz repository so the tags are useful when folks are used to talking about > useing a particular version of Seaside31. To replace symbolic versions > (like #release3 or #release3.1) we have introduced pattern matching for > tags. You can use the following github url to load the latest version of > 3.1: > > github://GsDevKit/Seaside31:3.1.?/repository > > >> I have stared your repos to make sure I get keep updated in any progress >> you make. I plan also to go back and re read that metacello chapter to >> better understand metacello. >> > > Take a look at the Metacello User Guide[1] as well for information about > using the Metacello Scripting API. > > [1] > https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUse… > > >> >> Thank you very much for your hard work, keep rocking :) >> >> > Haha, my pleasure! > > Dale > >

Nov. 15, 2014

Re: [Pharo-dev] [Bloc] Getting involved

by kilon alios

and of course it did not occur to me to search is smalltalkhub ! Yeah sorry that was an obvious one. On Sat, Nov 15, 2014 at 11:38 PM, stepharo <stepharo(a)free.fr> wrote: > > is there a place where we can check the code and see what Bloc is all > about ? > > > AlainPlantec > Bloc project > If I get enough time I will write a doc.... now just a empty draft. > > > On Sat, Nov 15, 2014 at 9:59 PM, stepharo <stepharo(a)free.fr> wrote: > >> >> On 11/11/14 00:43, Santiago Bragagnolo wrote: >> >>> Hi Guys, (Alan and Steph punctually) I want to comment I am getting >>> involved with Bloc, since i need to draw several things and i need an >>> Athens canvas. >>> >>> I am checking if it is the best tool for my needs. In any case I am >>> doing some contributions that i would like to commit and to share. Actually >>> i am working on draft a window, a tool bar, a button based on images and >>> animations. >>> >>> Then, there is any mailing list for Bloc? How is the push-request cycle? >>> >> >> Alain told me that you should design a widget and based on the quality >> he will let you commit :) >> I'm confident. So let us know which widget you want to work on. >> >> Stef >> >>> >>> Thanks :). >>> >>> Santiago. >>> >>> >> >> > >

Nov. 15, 2014

Re: [Pharo-dev] Configurations and Github for a specialised configuration browswe

by Dale Henrichs

On Sat, Nov 15, 2014 at 9:54 AM, kilon alios <kilon.alios(a)gmail.com> wrote: > Travis seems like an overkill for me right now. Sure if I was bombarded by > pull requests from other developers but in reality I work alone . But I > will definitely keep it in mind in case my projects become so popular that > people start to send me pull requests regularly. > Makes sense. > > All I wanted was an easy way to install code from github to pharo without > the need to install git and you gave me that. Next step is to see how I > would integrate github with pharo better, should I use Configuration > versions or is it better to use branches ? I am more orientated towards > branches. > With git I think that configurations are really no longer necessary ... I prefer to use branches to isolate development work from the master branch (topic branches) and then use tags to identify release points ... with travis-ci validating the commits, I can do continuous deployment on the master branch ... For Seaside31 we are using tags to stay in sync with the mcz repository so the tags are useful when folks are used to talking about useing a particular version of Seaside31. To replace symbolic versions (like #release3 or #release3.1) we have introduced pattern matching for tags. You can use the following github url to load the latest version of 3.1: github://GsDevKit/Seaside31:3.1.?/repository > I have stared your repos to make sure I get keep updated in any progress > you make. I plan also to go back and re read that metacello chapter to > better understand metacello. > Take a look at the Metacello User Guide[1] as well for information about using the Metacello Scripting API. [1] https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUse… > > Thank you very much for your hard work, keep rocking :) > > Haha, my pleasure! Dale

Nov. 15, 2014

Re: [Pharo-dev] ValueHolder analysis

by stepharo

I get dizzy (may be time to go to sleep) but I wonder why do we need to check first the the window changed and after that it got closed? Especially since whenWindowChanged: presuppose that we have access to window. Am I missing something? self whenWindowChanged: [ :w | w whenClosedDo: [ self clear ] ]. ComposableModel>>whenWindowChanged: aBlock window whenChangedDo: aBlock WindowModel>>whenClosedDo: aBlock isClosedHolder whenChangedDo: [:value | value ifTrue: [ aBlock value ] ]

Nov. 15, 2014

Re: [Pharo-dev] ValueHolder analysis

by stepharo

initializePresenter "Used to specify the subwidgets, and/or to bind them together" "By default, do not do anything" extentHolder whenChangedDo: [:ex | self widget ifNotNil: [:widget | (widget respondsTo: #extent:) ifTrue: [ widget extent: ex ]]]. may be by design the ifNotNil should not be needed and the respondsTo too.... pffff.

Nov. 15, 2014

Re: [Pharo-dev] [NB] NativeBoost and optCoerceNilToNull

by stepharo

Igor Could you document this part of NB? Write one page on your old blog so that after we can turn it into a real doc. Stef On 15/11/14 22:28, Igor Stasenko wrote: > > > On 15 November 2014 15:53, Max Leske <maxleske(a)gmail.com > <mailto:maxleske@gmail.com>> wrote: > > Once again Iâm struggling with NativeBoost. Iâm trying to use > optCoerceNilToNull with this function: > > ^self call: #(LGitReturnCodeEnum git_commit_create( > LGitId * theCommitId, > LGitRepository repo, > String update_ref, > LGitSignature * theAuthor, > LGitSignature * theCommitter, > String message_encoding, > String theMessage, > LGitTree theTree, > int parent_count, > LGitCommit * parentsPointer)) options: #( optCoerceNilToNull ) > > The last argument can be NULL, per documentation, (no parents). > LGitCommit is a subclass of NBExternalObject and apparently > NBExternalObjctType>>pushAsPointer: does *not* use the > optCoerceNilToNull option (the super implementation in > NBExternalType>>pushAsPointer: however does). The upshot of course > is that the call fails with âan instance of LGitCommit expectedâ. > > My questions: > - The documentation says: > > > "#optCoerceNilToNull" > "passing nil as a pointer-type argument, converts it to C NULL â > > but apparently this doesnât apply to every pointer type. Should > the documentation be updated? > - Why does NBExternlObjectType not use optCoerceNilToNull? I donât > want to use tricks to pass null if I donât have to. > > > perhaps because it is not there? :) > So, lets add it. > > - Related: there are instances where even non-pointer arguments > are allowed to be NULL. Why does optCoerceNilToNull only work for > pointer types? > > like what? Suppose the argument type is a structure, e.g > "struct foo bar", that is non-pointer type. What in this case the NULL > value for the structure? > > Igor! Help! :) > > Cheers, > Max > > > > > -- > Best regards, > Igor Stasenko.

Nov. 15, 2014

Re: [Pharo-dev] [Bloc] Getting involved

by stepharo

> is there a place where we can check the code and see what Bloc is all > about ? AlainPlantec Bloc project If I get enough time I will write a doc.... now just a empty draft. > > On Sat, Nov 15, 2014 at 9:59 PM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > > On 11/11/14 00:43, Santiago Bragagnolo wrote: > > Hi Guys, (Alan and Steph punctually) I want to comment I am > getting involved with Bloc, since i need to draw several > things and i need an Athens canvas. > > I am checking if it is the best tool for my needs. In any case > I am doing some contributions that i would like to commit and > to share. Actually i am working on draft a window, a tool bar, > a button based on images and animations. > > Then, there is any mailing list for Bloc? How is the > push-request cycle? > > > Alain told me that you should design a widget and based on the > quality he will let you commit :) > I'm confident. So let us know which widget you want to work on. > > Stef > > > Thanks :). > > Santiago. > > > >

Nov. 15, 2014