Now when I say FFI this is alien if alien is available. since alien deals better with callbacks apparently.
Bill my plate is full :) but this is not a problem of vision. We have cool and real dreams for Pharo. Now we should be darned pragmatic. One stone at a time... but millions of time. This is why your 30 min a week for pharo makes a real difference. Back hakcing on Rapckage. Stef On Apr 20, 2010, at 9:56 PM, csra...@bol.com.br wrote: > <blatant warning> > Due the way I envisage using Pharo I have stakes in these matter¹. Please > read with a grain of salt. > </blatant warning> > > I think the 'interpretation' of Stef's question is being different from > person to person. The issue Wilhelm brings it seems to me more of "what > priority we give to have FFI working". > > Putting it as part of core IMHO has more chances of having it prioritized as > we think in the release of 1.1 that if we leave it as a package, because it > may be still broken and 1.1 may be called ready for shipping. > > I also do agree that FFI is infrastructure and as such has to be seen as > core, and since the ability to have Pharo more useful depends on the > possibility to use a lot of code we are not able (in some case even not > willing to) to rewrite in Pharo Smalltalk, I vote to have it as default and > strive to have it working as soon as possible. > > my 0.01999... > > > -- > Cesar Rabak > > [1] If you're curious, I'm interested in seeing R http://www.r-project.org/ > working with Pharo (at least as Martin Rubi's smallRApi for Dolphin) > > Em 20/04/2010 10:15, Mariano Martinez Peck < marianop...@gmail.com > escreveu: > > > > > 2010/4/20 Schwab,Wilhelm K <bsch...@anest.ufl.edu> > > > > Mariano, > > FFI, use of OS threads and callbacks are *very* basic needs that we should > support. IMHO, we should be focused on making them work, not on classifying > what is internal or external. > > > > > But is has nothing to do with what Stef asked: "Do we add FFI by default in > 1.1?" > In my opinion, it shouldn't be by default. > > However, this doesn't mean that we don't support FFI. And I am not saying to > focus in internal or external. I just answer Stef question with my opinion. > > Cheers > > Mariano > > > > > > > Bill > > > > > > > From: pharo-project-boun...@lists.gforge.inria.fr > [mailto:pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Mariano > Martinez Peck > Sent: Monday, April 19, 2010 9:49 PM > To: Pharo-project@lists.gforge.inria.fr > Subject: Re: [Pharo-project] FFI in 1.1 > > > > > > On Thu, Apr 15, 2010 at 9:31 PM, Stéphane Ducasse <stephane.duca...@inria.fr> > wrote: > > Hi all > > Do we add FFI by default in 1.1? > > > Noooooooooo!!! > > I wouldn't include neither FFI or Alien FFI in neither PharoCore or PharoDev > image. > > FFI is an EXTERNAL package, NOT core, neither a dev tool. > > That's only my opinion. > > Cheers > > Mariano > This was the plan so. > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
