- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Cog/FFI Return Values

by Ken Treis

On Mar 15, 2011, at 3:36 PM, Eliot Miranda wrote: > I expect that if the standard FFI plugin answers an instance of OopType64 then you've found a bug in the ReentrantFFIPlugin. If you're brave you'll have a look at both plugins and try and verify that that's the case. But I have to say that the FFI plugins are not simple. Brave, yes. Smart, no. Here's what it looks like to my untrained eye: 1. When the ExternalFunction is compiled, the return argType is not flagged as a structure. So the primitives, old and new, see this as a regular non-struct callout, but with return class = OopType64. So far, so good. 2. The old plugin had this one-slot "wrapping" capability at the bottom of #ffiCreateReturn: (which is called only for non-pointer, non-structure functions): ffiRetClass := interpreterProxy popRemappableOop. ffiRetClass == interpreterProxy nilObject ifTrue:[ "Just return oop" ^interpreterProxy push: retOop]. "Otherwise create an instance of external structure and store the return oop" interpreterProxy pushRemappableOop: retOop. retOop := interpreterProxy instantiateClass: ffiRetClass indexableSize: 0. oop := interpreterProxy popRemappableOop. interpreterProxy storePointer: 0 ofObject: retOop withValue: oop. ^interpreterProxy push: retOop. 3. There's some very similar code in FFIPlugin>>ffiCreateReturnStruct and ReentrantIA32FFIPlugin>>ffiReturnStruct:ofType:in: -- the main difference is a memcpy(). Am I on the right track? If so, how would you like to see the code structured to get this feature restored? We could add a new wrap-if-necessary return method, or we could try to reuse #ffiReturnStruct:ofType:in: if we guarded the memcpy() with a flag check for FFIFlagStructure. Or maybe there's a cleaner solution that's beyond my hazy view at the moment. -- Ken Treis Miriam Technologies, Inc.

March 16, 2011

Re: [Pharo-project] Breakpoints in Pharo

by Marcus Denker

On Mar 16, 2011, at 8:58 PM, Sven Van Caekenberghe wrote: > > On 16 Mar 2011, at 19:48, Marcus Denker wrote: > >> >> On Mar 16, 2011, at 7:41 PM, Noury Bouraqadi wrote: >> >>> A break point should not turn the MC package into dirty as opposite to inserting a self halt or self haltIf:[...]. >>> >> and >> -> one could remove all breakpoints with a menu entry >> -> disable but not remove >> -> watchpoints (viewers for values and expressions), even conditonal >> -> nice integration in the IDE... >> >> Marcus > > I have elementary breakpoint support in my Pharo images (Toggle Breakpoint in the Selector menu) and I use it all the time and I am quite happy with it (together with 'Debug it'). Indeed more options would be nice. But at least I don't have to do a self halt any more in most cases. > > I don't know how it works, I guess it comes with OB ? I think it was a [ENH] sent to the squeak mailinglist a looong time ago... see this mail from 2003: At 8:43 PM +0100 3/3/03, Torsten.Bergmann at phaidros.com wrote: >Hi all, > >this is an older but usefull little change set adding breakpoint >support to squeak. File it in and use the context menu in the >method pane of a browser to set/reset a breakpoint >for the method. It's very usefull since you dont have >to write a "self halt" if you want to debug a single >method. > >It was coded by Ernest Micklei from Philemonworks (thanks a >lot Ernest !!!) in an older squeak version. A short test >in 3.4 final showed it is still usefull. Note that it >doesnt work if you have RB installed. If others find it usefull >too we can register it on SqueakMap or add it to the base image. > It lived on SqueakMap for a while http://map.squeak.org/package/07469ced-289a-4b6f-bd17-27ec567e681a I guess we merged it in Squeak 3.6 or 3.7 in the image. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 16, 2011

[Pharo-project] [COTDC] - 33 StrikeFontSet

by laurent laffont

Today: StrikeFontSet Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

March 16, 2011

Re: [Pharo-project] [COTDC] 32 - MCScanner

by laurent laffont

On Wed, Mar 16, 2011 at 8:08 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > To read the metadata (package name, version info, ancestry, > dependencies) from .mcz files. > Thanks Lukas. I put: I scan / tokenize metadata (package name, version info, ancestry, dependencies, ...) found in .mcz files. For example, try: MCScanner scan: '(name ''MyPackage-ll.6'' message ''Fix bug xxx'' id ''b21dbd73-f1c3-2746-a3cc-92f1d4edea28'')' readStream Laurent. > > Lukas > > On 16 March 2011 20:05, laurent laffont <laurent.laffont(a)gmail.com> wrote: > > Someone ? > > I had a quick look. I've seen that > > self assert: (MCScanner scan: '(a #b c)' readStream) = #(a #b c) > > but I still don't know why we need this > > Laurent. > > On Tue, Mar 15, 2011 at 6:28 PM, laurent laffont < > laurent.laffont(a)gmail.com> > > wrote: > >> > >> Today: MCScanner > >> > >> Comment Of The Day Contest - One Day One Comment > >> Rules: > >> #1: Each day a not commented class is elected. Each day the best comment > >> will be integrated with name of the author(s). > >> #2: If you cannot comment it, deprecate it. > >> Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > >> Laurent > > > > > > -- > Lukas Renggli > www.lukas-renggli.ch > >

March 16, 2011

Re: [Pharo-project] Breakpoints in Pharo

by Schwab,Wilhelm K

Dmitri, I am pretty sure the discussion is over having some way to mark a line as a breakpoint w/o having to insert #halt and accepting the change - like you would set a breakpoint in C IDE. The truth is that I have been using #halt that for so long that I miss it when working in other languages!! :) Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Dmitri Zagidulin [dmitri(a)zagidulin.net] Sent: Wednesday, March 16, 2011 11:46 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Breakpoints in Pharo How is a breakpoint different from a 'self halt' statement? On Wed, Mar 16, 2011 at 11:41 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > no news on this front. > We are working on infrastructure right now > - better code model > - compiler > - package > - network > - redoing the tools. > > So from a user experience it may look the same but it is a real set of important changes below the surface > that will make us far more agile in the future. > > When we will get done we will be able to move faster on other points. > > Stef > > >> Dear Pharoers, >> >> What is the current state of affairs on breakpoints? >> >> Breakpoins is a thing I really miss when I'm working on Pharo, comparing >> to working on VisualWorks... >> >> This is in light of current question on StackOverflow: >> >> http://stackoverflow.com/questions/5322497/how-can-i-set-a-breakpoint-in-sq… >> >> Best regards >> Janko >> >> -- >> Janko MivÅ¡ek >> Aida/Web >> Smalltalk Web Application Server >> http://www.aidaweb.si >> > > >

March 16, 2011

Re: [Pharo-project] Breakpoints in Pharo

by Sven Van Caekenberghe

On 16 Mar 2011, at 19:48, Marcus Denker wrote: > > On Mar 16, 2011, at 7:41 PM, Noury Bouraqadi wrote: > >> A break point should not turn the MC package into dirty as opposite to inserting a self halt or self haltIf:[...]. >> > and > -> one could remove all breakpoints with a menu entry > -> disable but not remove > -> watchpoints (viewers for values and expressions), even conditonal > -> nice integration in the IDE... > > Marcus I have elementary breakpoint support in my Pharo images (Toggle Breakpoint in the Selector menu) and I use it all the time and I am quite happy with it (together with 'Debug it'). Indeed more options would be nice. But at least I don't have to do a self halt any more in most cases. I don't know how it works, I guess it comes with OB ? Sven PS: See Lukas' mail from sept 10 2010

March 16, 2011

Re: [Pharo-project] Breakpoints in Pharo

by Benoit St-Jean

+1 for breakpoints ----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein)

March 16, 2011

Re: [Pharo-project] Breakpoints in Pharo

by Reg Krock

+1 --- it would be very nice > A break point should not turn the MC package into dirty as opposite to >inserting a self halt or self haltIf:[...]. > and -> one could remove all breakpoints with a menu entry -> disable but not remove -> watchpoints (viewers for values and expressions), even conditonal -> nice integration in the IDE... Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. On Mar 16, 2011, at 7:41 PM, Noury Bouraqadi wrote:

March 16, 2011

Re: [Pharo-project] [COTDC] 32 - MCScanner

by Lukas Renggli

To read the metadata (package name, version info, ancestry, dependencies) from .mcz files. Lukas On 16 March 2011 20:05, laurent laffont <laurent.laffont(a)gmail.com> wrote: > Someone ? > I had a quick look. I've seen that > self assert: (MCScanner scan: '(a #b c)' readStream) = #(a #b c) > but I still don't know why we need this > Laurent. > On Tue, Mar 15, 2011 at 6:28 PM, laurent laffont <laurent.laffont(a)gmail.com> > wrote: >> >> Today: Â MCScanner >> >> Comment Of The Day Contest - One Day One Comment >> Rules: >> #1: Each day a not commented class is elected. Each day the best comment >> will be integrated with name of the author(s). >> #2: If you cannot comment it, deprecate it. >> Results:Â http://code.google.com/p/pharo/wiki/CommentOfTheDayContest >> Laurent > -- Lukas Renggli www.lukas-renggli.ch

March 16, 2011

Re: [Pharo-project] [COTDC] 32 - MCScanner

by laurent laffont

Someone ? I had a quick look. I've seen that self assert: (MCScanner scan: '(a #b c)' readStream) = #(a #b c) but I still don't know why we need this Laurent. On Tue, Mar 15, 2011 at 6:28 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > Today: MCScanner > > > Comment Of The Day Contest - One Day One Comment > Rules: > #1: Each day a not commented class is elected. Each day the best comment > will be integrated with name of the author(s). > #2: If you cannot comment it, deprecate it. > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > Laurent >

March 16, 2011