- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Status of Alien FFI

by StÃ©phane Ducasse

yes this is one of my dream but .... I'm not good enough to make it come true. Stef On Sep 18, 2009, at 6:40 PM, Lawson English wrote: > Johan Brichau wrote: >> On 16 Sep 2009, at 20:37, Ken Treis wrote: >> >> >>> * I'm creating a partial Alien library for GemStone so that I can >>> use the CairoGraphics package in both Pharo and GLASS. But on >>> x86-64, there there's a size difference between a pointer/long and >>> an integer. It'd be nice to have some more explicit APIs on Alien, >>> so I could say "Alien newCInteger" or "Alien newCLong" and have the >>> platform return me the proper size Alien. Even without the platform >>> size differences, it seems awkward to use "Alien newC: 4" everywhere >>> I want an integer, "Alien newC: 8" where I want a double, etc. >>> >> >> Exactly. >> >> It becomes worse once you start having structs and nested structs or >> structs with pointers to structs ;-) >> >> I'm using Alien as the FFI to port JavaConnect from Visualworks to >> Pharo/Squeak. As you say, it is a pain to work at such a low-level >> compared to the DLLCC in VW. I am planning to do some work on >> creating >> a higher-level interface for it such that we can operate it as you >> mention, including the correct bytesizes for all platforms. >> >> At the moment, I'm mostly focusing on getting the port to work right >> before I start creating an interface on top of the current Alien >> interface. >> >> >> > > Something to keep in mind is the need for a straightforward way of > going > the other way: John Mcintosh's port of the Squeak VM to iPhone implies > that the same thing could be done in other Lua-ish situations, > allowing > people to use smalltalk syntax for game scripting. With the right > libraries for an IDE, I would think squeak could be very attractive to > at least some people in place of/in addition to using Lua. > > > Lawson > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 18, 2009

Re: [Pharo-project] Status of Alien FFI

by Lawson English

Johan Brichau wrote: > On 16 Sep 2009, at 20:37, Ken Treis wrote: > > >> * I'm creating a partial Alien library for GemStone so that I can >> use the CairoGraphics package in both Pharo and GLASS. But on >> x86-64, there there's a size difference between a pointer/long and >> an integer. It'd be nice to have some more explicit APIs on Alien, >> so I could say "Alien newCInteger" or "Alien newCLong" and have the >> platform return me the proper size Alien. Even without the platform >> size differences, it seems awkward to use "Alien newC: 4" everywhere >> I want an integer, "Alien newC: 8" where I want a double, etc. >> > > Exactly. > > It becomes worse once you start having structs and nested structs or > structs with pointers to structs ;-) > > I'm using Alien as the FFI to port JavaConnect from Visualworks to > Pharo/Squeak. As you say, it is a pain to work at such a low-level > compared to the DLLCC in VW. I am planning to do some work on creating > a higher-level interface for it such that we can operate it as you > mention, including the correct bytesizes for all platforms. > > At the moment, I'm mostly focusing on getting the port to work right > before I start creating an interface on top of the current Alien > interface. > > > Something to keep in mind is the need for a straightforward way of going the other way: John Mcintosh's port of the Squeak VM to iPhone implies that the same thing could be done in other Lua-ish situations, allowing people to use smalltalk syntax for game scripting. With the right libraries for an IDE, I would think squeak could be very attractive to at least some people in place of/in addition to using Lua. Lawson

Sept. 18, 2009

Re: [Pharo-project] collapsable pane

by Tudor Girba

That looks promising. Thanks, Doru On 18 Sep 2009, at 10:07, Damien Cassou wrote: > On Fri, Sep 18, 2009 at 9:28 AM, Tudor Girba <girba(a)iam.unibe.ch> > wrote: >> Is there a Morphic widget that would allow a pane to be collapsed? > > Expander morph maybe? > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Problem solving efficiency grows with the abstractness level of problem understanding."

Sept. 18, 2009

[Pharo-project] [ANN] Smalltalks 2009 / FAST website

by Andres Valloud

Greetings, The FundaciÃ³n Argentina de Smalltalk, FAST :), is pleased to announce the Smalltalks 2009 website. The address is http://www.fast.org.ar Enjoy! Andres.

Sept. 18, 2009

Re: [Pharo-project] collapsable pane

by Damien Cassou

On Fri, Sep 18, 2009 at 9:28 AM, Tudor Girba <girba(a)iam.unibe.ch> wrote: > Is there a Morphic widget that would allow a pane to be collapsed? Expander morph maybe? -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Sept. 18, 2009

Re: [Pharo-project] Status of Alien FFI

by StÃ©phane Ducasse

Martin indeed it would be great to have a kind of standard On Sep 18, 2009, at 12:57 AM, Martin McClure wrote: > Johan Brichau wrote: >> On 16 Sep 2009, at 20:37, Ken Treis wrote: >> >>> * I'm creating a partial Alien library for GemStone so that I can >>> use the CairoGraphics package in both Pharo and GLASS. But on >>> x86-64, there there's a size difference between a pointer/long and >>> an integer. It'd be nice to have some more explicit APIs on Alien, >>> so I could say "Alien newCInteger" or "Alien newCLong" and have the >>> platform return me the proper size Alien. Even without the platform >>> size differences, it seems awkward to use "Alien newC: 4" everywhere >>> I want an integer, "Alien newC: 8" where I want a double, etc. >> >> Exactly. >> >> It becomes worse once you start having structs and nested structs or >> structs with pointers to structs ;-) >> >> I'm using Alien as the FFI to port JavaConnect from Visualworks to >> Pharo/Squeak. As you say, it is a pain to work at such a low-level >> compared to the DLLCC in VW. I am planning to do some work on >> creating >> a higher-level interface for it such that we can operate it as you >> mention, including the correct bytesizes for all platforms. >> >> At the moment, I'm mostly focusing on getting the port to work right >> before I start creating an interface on top of the current Alien >> interface. > > I'd like to work toward a standard FFI that works across many > Smalltalk > dialects. Right now, it's too hard to port packages such as > CairoGraphics that call large external libraries. A year ago, I tried > porting CairoGraphics from VW to an early version of GemStone's FFI. > It > was way too much work. > > And GemStone/S 64-bit 3.0, due out probably sometime next year, will > have a completely new FFI. It's probably not too late to influence the > design for better compatibility. > > Is Alien, possibly with some changes, a suitable cross-platform > cross-dialect FFI standard? Or is it too low-level? > > Regards, > > -Martin > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 18, 2009

Re: [Pharo-project] Seach for Tcl Expect equivalent

by Vicnet

Hello, David T. Lewis wrote: > >> Expect is a librarie/tools in perl or Tcl that is aim to control a >> process. > I do not know of anything equivalent to Expect, but if you are using > OSProcess and CommandShell, then the scripting methods in CommandShell > such as #script:onFailureDo: and #if:then:else: may be of some interest. > You're right. Expect is something like that but with more possibilities on what an application could put on stdout. Thanks for the idea. a+ Vicnet -- View this message in context: http://n2.nabble.com/Seach-for-Tcl-Expect-equivalent-tp3662709p3667924.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Sept. 18, 2009

[Pharo-project] collapsable pane

by Tudor Girba

Hi, Is there a Morphic widget that would allow a pane to be collapsed? Cheers, Doru -- www.tudorgirba.com "Next time you see your life passing by, say 'hi' and get to know her."

Sept. 18, 2009

Re: [Pharo-project] Seach for Tcl Expect equivalent

by Vicnet

Hello, David T. Lewis wrote: > >> Expect is a librarie/tools in perl or Tcl that is aim to control a >> process. > I do not know of anything equivalent to Expect, but if you are using > OSProcess and CommandShell, then the scripting methods in CommandShell > such as #script:onFailureDo: and #if:then:else: may be of some interest. > You're right. Expect is something like that but with more possibilities on what an application could put on stdout. Thanks for the idea. a+ Vicnet -- View this message in context: http://n2.nabble.com/Seach-for-Tcl-Expect-equivalent-tp3662709p3667920.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Sept. 18, 2009

Re: [Pharo-project] Seach for Tcl Expect equivalent

by David T. Lewis

On Thu, Sep 17, 2009 at 05:32:36AM -0700, Vicnet wrote: > > Hello, > > Expect is a librarie/tools in perl or Tcl that is aim to control a process. > You could send command on the stdin and wait for answer on stdout, then > react on this event (thant why it is call 'expect'). > > Uselfull for executable tests, or control an automatic telnet session ... > > I know OSProcess to launch executable and play with stdin/stdout but it's > not exactly what do Expect. > > > Do you know something like that on Pharo ? I do not know of anything equivalent to Expect, but if you are using OSProcess and CommandShell, then the scripting methods in CommandShell such as #script:onFailureDo: and #if:then:else: may be of some interest. There are examples in CommandShellTestCase in category "testing-scripts". Basically it works like this: result := CommandShell new script: 'who help ls -l NOSUCHFILE help' onFailureDo: [:p | 'the pipeline collection that failed was ', p printString]. or this: CommandShell new if: 'who ls NOSUCHFILE pwd' then: ['the script succeeded'] else: ['the script failed'] Dave

Sept. 17, 2009