October 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Probably stupid... question about string printString.

by Torsten Bergmann

Alistair Grant wrote: > I can't comment on the original thinking behind this The original thinking is simple and as the name says: you want to print the object (even when it is a string) to be print in a string. So it always is a "printObjectInString" instead of a "printObjectAsString" behavior. Also the resulting string often is a string to easily reconstruct the object. So it is not a conversion method. There is #asString for that. > If we're displaying values such as numbers and strings in a UI, e.g. > table, we normally don't want the strings always enclosed in quotes. There is #displayString for this task (which may return the printString or is overwritten) and this is common in nearly all Smalltalks I know. Bye T.

Oct. 22, 2017

Re: [Pharo-dev] System Update Failure from #60510 -> #60513

by Sean P. DeNigris

Marcus Denker-4 wrote > yes, can you send it to me? I will add it. It's in the Pharo60Inbox. Of course I can still send it to you if that would helpâ¦ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 22, 2017

Re: [Pharo-dev] Probably stupid... question about string printString.

by Alistair Grant

Hi Nicolas, On Sat, Oct 21, 2017 at 10:12:06PM +0200, Nicolas Cellier wrote: > IOW, if you want to print 'foo', just print 'foo', but don't print 'foo' > printString. > > 2017-10-21 22:10 GMT+02:00 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> > : > > No. nextPutAll: self is not a good solution at all. > Try it, and you'll get foo, not 'foo'. > > 'foo' printString has exactly 5 letters: $' $f $o $o $' so it does what you > want. But what I want is the 3 letters in foo. Think about displaying a table of values. If it contains a mixture of numbers and strings, what I want to see is: 1 | string one | 3.1415 | string two not: 1 | 'string one' | 3.1415 | 'string two' If I want the second form (with quotes) I can use #storeString / #storeOn:. What is the one message that I can send to a mixture of numbers and strings that will return a string (or write to a stream) that will display as shown in the first example above? Thanks, Alistair > The problem is when you want to print 'foo' printString. > You are in fact doing 'foo' printString printOn: aStream, IOW aStream > nextPutAll: 'foo' printString printString. > > > 2017-10-21 21:12 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > > Yes this is my point. I was surprised to get ' on the transcript. > > Stef > > On Sat, Oct 21, 2017 at 7:49 PM, Alistair Grant <akgrant0710(a)gmail.com> > wrote: > > On Sat, Oct 21, 2017 at 05:28:21PM +0200, Stephane Ducasse wrote: > >> Hi > >> > >> I would like to really understand why > >> 'foo' printString > >> >>> > >> '''foo''' > >> > >> and not why this is not > >> > >> 'foo' > >> > >> itself. > >> > >> Stef > > > > I can't comment on the original thinking behind this, but I agree > that > > something like: > > > > > > String>>printOn: aStream > > "Represent the receiver on the supplied stream" > > > > aStream nextPutAll: self > > > > > > > > would be much better. > > > > If we're displaying values such as numbers and strings in a UI, e.g. > > table, we normally don't want the strings always enclosed in quotes. > > > > Cheers, > > Alistair > > > > > > > > >

Oct. 21, 2017

Re: [Pharo-dev] Probably stupid... question about string printString.

by Nicolas Cellier

IOW, if you want to print 'foo', just print 'foo', but don't print 'foo' printString. 2017-10-21 22:10 GMT+02:00 Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com>: > No. nextPutAll: self is not a good solution at all. > Try it, and you'll get foo, not 'foo'. > > 'foo' printString has exactly 5 letters: $' $f $o $o $' so it does what > you want. > > The problem is when you want to print 'foo' printString. > You are in fact doing 'foo' printString printOn: aStream, IOW aStream > nextPutAll: 'foo' printString printString. > > > 2017-10-21 21:12 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > >> Yes this is my point. I was surprised to get ' on the transcript. >> >> Stef >> >> On Sat, Oct 21, 2017 at 7:49 PM, Alistair Grant <akgrant0710(a)gmail.com> >> wrote: >> > On Sat, Oct 21, 2017 at 05:28:21PM +0200, Stephane Ducasse wrote: >> >> Hi >> >> >> >> I would like to really understand why >> >> 'foo' printString >> >> >>> >> >> '''foo''' >> >> >> >> and not why this is not >> >> >> >> 'foo' >> >> >> >> itself. >> >> >> >> Stef >> > >> > I can't comment on the original thinking behind this, but I agree that >> > something like: >> > >> > >> > String>>printOn: aStream >> > "Represent the receiver on the supplied stream" >> > >> > aStream nextPutAll: self >> > >> > >> > >> > would be much better. >> > >> > If we're displaying values such as numbers and strings in a UI, e.g. >> > table, we normally don't want the strings always enclosed in quotes. >> > >> > Cheers, >> > Alistair >> > >> > >> >> >

Oct. 21, 2017

Re: [Pharo-dev] Probably stupid... question about string printString.

by Nicolas Cellier

No. nextPutAll: self is not a good solution at all. Try it, and you'll get foo, not 'foo'. 'foo' printString has exactly 5 letters: $' $f $o $o $' so it does what you want. The problem is when you want to print 'foo' printString. You are in fact doing 'foo' printString printOn: aStream, IOW aStream nextPutAll: 'foo' printString printString. 2017-10-21 21:12 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > Yes this is my point. I was surprised to get ' on the transcript. > > Stef > > On Sat, Oct 21, 2017 at 7:49 PM, Alistair Grant <akgrant0710(a)gmail.com> > wrote: > > On Sat, Oct 21, 2017 at 05:28:21PM +0200, Stephane Ducasse wrote: > >> Hi > >> > >> I would like to really understand why > >> 'foo' printString > >> >>> > >> '''foo''' > >> > >> and not why this is not > >> > >> 'foo' > >> > >> itself. > >> > >> Stef > > > > I can't comment on the original thinking behind this, but I agree that > > something like: > > > > > > String>>printOn: aStream > > "Represent the receiver on the supplied stream" > > > > aStream nextPutAll: self > > > > > > > > would be much better. > > > > If we're displaying values such as numbers and strings in a UI, e.g. > > table, we normally don't want the strings always enclosed in quotes. > > > > Cheers, > > Alistair > > > > > >

Oct. 21, 2017

Re: [Pharo-dev] Some segfault crashes and freezes when trying to re-run saved pharo 7 images

by Stephane Ducasse

Thanks thomas we should find the problem. Stef On Fri, Oct 20, 2017 at 3:57 PM, Thomas Dupriez <thomas.dupriez(a)ens-paris-saclay.fr> wrote: > Hello, > > I've had a few issues with Pharo 7 lately. After downloading pharo 7 images, > doing some work in them and saving them, the images either instantly crashe > or freeze when I try to re-run them. > If that helps, I was working with and on the calypso browser. > > Attached are the crash dump files from some of these faulty images. > > vm version: 201708271955 > image version: 6521 > OS: Ubuntu 16.04 LTS > > Cheers, > Thomas >

Oct. 21, 2017

Re: [Pharo-dev] UnifiedFFI Docs

by Stephane Ducasse

Esteban will probably reply to this thread On Thu, Oct 19, 2017 at 10:34 PM, Todd Blanchard <tblanchard(a)mac.com> wrote: > I have found the problem with VoidPointer3 generating accessors. > > No idea how to contribute back a fix but this is what I've found. > > FFITypeArrayType>>annonymousClassCreator > ^ String streamContents: [ :stream | > stream > nextPutAll: '(FFITypeArray ofType: '; > print: (self objectClass type isPointer ifTrue: [self externalTypeWithArity > printString] ifFalse: ['#',self objectClass type class]); > nextPutAll: ' size: '; > print: self objectClass numberOfElements; > nextPutAll: ')' ] > > Recalling that we are trying to come up with an accessor that can pull out a > void*[3], this produces > > '(FFITypeArray ofType: #FFIVoid size: 3)' > > which produces an error as FFIVoid's size is undefined. In general, this > will be wrong for any pointer type and will probably get the size > calculation wrong. > > Doing a little digging I find that > > FFITypeArray>>ofType: aType size: aSize > > delegates resolution of aType to FFIExternalType>>resolveType:aType and this > can take all kinds of different things including the native type name. > > It would be better if this generated the native name for pointers. > > (FFITypeArray ofType: 'void*' size: 3) > > So I changed it to: > > FFITypeArrayType>>annonymousClassCreator > ^ String streamContents: [ :stream | > stream > nextPutAll: '(FFITypeArray ofType: '; > print: (self objectClass type isPointer > ifTrue: [self externalTypeWithArity printString] > ifFalse: ['#',self objectClass type class]); > nextPutAll: ' size: '; > print: self objectClass numberOfElements; > nextPutAll: ')' ] > > and this seems to work fine. > > Onwards... > > On Oct 19, 2017, at 7:18 AM, Todd Blanchard <tblanchard(a)mac.com> wrote: > > Thatâs great - itâs been kind of magical but a couple things have changed > since you wrote it and some bugs have crept into ffi. > > Right now Iâm finding the generated accessor for the VoidPointer3 is > actually generating a void 3 accessor and that doesnât work. I spent all day > yesterday tracking it to the accessor generating code. > > Sent from the road > > On Oct 18, 2017, at 22:29, Ben Coman <btc(a)openinworld.com> wrote: > > > > On Thu, Oct 19, 2017 at 1:05 AM, Todd Blanchard <tblanchard(a)mac.com> wrote: >> >> I'm working through Ben's great blog post about playing with libclang and >> I am puzzled by something. > > > Thx Todd. Knowing someone is looking at it encourages me to expand it. > I'm interested in looking at your specific questions, but it might not be > until next week after this stint of long work days. > > cheers -ben > > >> >> >> invalidateSessionData >> handle atAllPut: 0. >> >> zero;s out the handle. Cool. However, >> >> handle isNull >> >> does not return true despite it being used in the getString method as >> >> ^ handle isNull >> ifTrue: ['external memory invalidated by session restart'] >> ifFalse:[LibClang clang_getCString__cxString: self]. >> >> Looks like there should be an isNull on ByteArray that returns true if all >> bytes are zero but it isn't there. Was it dropped for some reason? >> >> >> >> On Oct 18, 2017, at 2:58 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> >> wrote: >> >> Sure the documentation could be better, that is definetly important, but >> is already good enough and UFFI is a very technical subject much more suited >> to a mailing list . Its not physical possible to cover the massive potential >> of UFFI. >> >> On Wed, Oct 18, 2017 at 9:32 AM Stephane Ducasse <stepharo.self(a)gmail.com> >> wrote: >>> >>> Please do not hesitate to do Pull Requests. >>> Luc told me that he wants to do a pass on it and Esteban promises that to >>> me >>> but he is super busy. >>> >>> Stef >>> >>> >>> On Wed, Oct 18, 2017 at 5:54 AM, Todd Blanchard <tblanchard(a)mac.com> >>> wrote: >>> > Wonderful! Thanks. >>> > >>> >> On Oct 17, 2017, at 3:45 PM, stephan <stephan(a)stack.nl> wrote: >>> >> >>> >> On 17-10-17 23:06, Todd Blanchard wrote: >>> >>> Anyone know what happened to this? >>> >>> >>> >>> https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre… >>> >> >>> >> https://github.com/SquareBracketAssociates/Booklet-uFFI >>> >> >>> >> has a link to a bintray pdf download >>> >> >>> >> Stephan >>> >> >>> >> >>> >> >>> > >>> > >>> >> > >

Oct. 21, 2017

Re: [Pharo-dev] Probably stupid... question about string printString.

by Stephane Ducasse

Yes this is my point. I was surprised to get ' on the transcript. Stef On Sat, Oct 21, 2017 at 7:49 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > On Sat, Oct 21, 2017 at 05:28:21PM +0200, Stephane Ducasse wrote: >> Hi >> >> I would like to really understand why >> 'foo' printString >> >>> >> '''foo''' >> >> and not why this is not >> >> 'foo' >> >> itself. >> >> Stef > > I can't comment on the original thinking behind this, but I agree that > something like: > > > String>>printOn: aStream > "Represent the receiver on the supplied stream" > > aStream nextPutAll: self > > > > would be much better. > > If we're displaying values such as numbers and strings in a UI, e.g. > table, we normally don't want the strings always enclosed in quotes. > > Cheers, > Alistair > >

Oct. 21, 2017

Re: [Pharo-dev] Some segfault crashes and freezes when trying to re-run saved pharo 7 images

by ClÃ©ment Bera

On Sat, Oct 21, 2017 at 6:23 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > #(FT2Handle FreeTypeCache FreeTypeSettings) do: [ :each | SessionManager >> default unregisterClassNamed: each ] >> > > How am I supposed to launch the script if it crashes on startup? I've > tried running from terminal but to no avail. > > ... I was talking about future images. If you want to save your already crashing image, the crash.dump says the VM crashes in FreeTypeFace(FT2Face)>newFaceFromExternalMemory:index: . So you need to interrupt that / change the behavior of one of the method leading to this behavior. What I would try: - start the image on a VM without Freetype (maybe you will have an error instead of a crash) - open a new image, and check what you could return immediately instead of executing one of the faulty method to start-up without a crash (For example, if I replace the method body of FreeTypeFace(FT2Face)>newFaceFromExternalMemory:index: by ^ self, does it crash ? If yes, pick another method upper in the crashing stack of crash.dump or return something else). Then, you can either: * start the image on the VMSimulator, set a break point on the method selector with the body you want to replace and change the runtime behavior to return the value you want instead. * open your crashing image with an hexadecimal editor, look for the bytecode sequence of the method with the body you want to replace, replace it with new bytecode to return the value you want. Save your image. Restart it on the VM. That kind of things. Best, > Thanks, > Peter > -- ClÃ©ment BÃ©ra Pharo consortium engineer https://clementbera.wordpress.com/ BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq

Oct. 21, 2017

Re: [Pharo-dev] Probably stupid... question about string printString.

by Alistair Grant

On Sat, Oct 21, 2017 at 05:28:21PM +0200, Stephane Ducasse wrote: > Hi > > I would like to really understand why > 'foo' printString > >>> > '''foo''' > > and not why this is not > > 'foo' > > itself. > > Stef I can't comment on the original thinking behind this, but I agree that something like: String>>printOn: aStream "Represent the receiver on the supplied stream" aStream nextPutAll: self would be much better. If we're displaying values such as numbers and strings in a UI, e.g. table, we normally don't want the strings always enclosed in quotes. Cheers, Alistair

Oct. 21, 2017