- Pharo-dev - lists.pharo.org

Anoying bug found in Artefact running in Windows 10

by casimiro barreto

Ok, Thanks to your help, the problem is solved. Nothing to do with Artefact but "imageStream := FileStream fileNamed: 'lsi-tec.jpg'." imageStream := FileSystem disk openFileStream: 'lsi-tec.jpg' writable: false. did the trick. Interesting is that FileStream works ok in Linux. Best regards, CdAB63 -- The information contained in this message is confidential and intended to the recipients specified in the headers. If you received this message by error, notify the sender immediately. The unauthorized use, disclosure, copy or alteration of this message are strictly forbidden and subjected to civil and criminal sanctions.

Oct. 22, 2017

Re: [Pharo-dev] Help for the mooc

by Stephane Ducasse

Apparently this is what the students themselves did. On Thu, Oct 19, 2017 at 11:40 PM, Ben Coman <btc(a)openinworld.com> wrote: > Was this fixed by replacing the redirect with an actual file? > I went to look at http://pharo.org/web/files/pharo.png > using Chrome "F12" Develop Tools to view the redirect, > and IIUC I directly got the PNG itself. Just checking I'm interpreting that > correctly. > > cheers -ben > > On Wed, Oct 18, 2017 at 2:33 PM, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: >> >> Tx! >> I should fix it but probably the videos are still using the old one. >> >> On Tue, Oct 17, 2017 at 10:36 PM, Sven Van Caekenberghe <sven(a)stfx.eu> >> wrote: >> > >> > >> >> On 17 Oct 2017, at 22:29, Stephane Ducasse <stepharo.self(a)gmail.com> >> >> wrote: >> >> >> >> Hi >> >> >> >> students have a problem with the following in Pharo 50 (we could not >> >> upgrade) >> >> >> >> (ZnEasy getPng: 'http://pharo.org/web/files/pharo.png') asMorph >> >> openInWindow >> >> >> >> >> >> ConnectionClosed : connection closed while waiting for data >> >> >> >> And well this is super annoying. >> >> >> >> Stef >> > >> > This is fixed in later versions. You can try the following: >> > >> > (ZnEasy getPng: 'http://pharo.org/files/pharo.png') asMorph >> > openInWindow. >> > >> > The reason that last one works is that http://pharo.org/files/pharo.png >> > is an http url that resolves directly, while >> > http://pharo.org/web/files/pharo.png redirects to an https equivalent which >> > can only be read with #serverName support. For this, you need not only a >> > more recent version of Zinc, but also a newer VM with a more recent SSL >> > plugin. >> > >> > Sven >> >

Oct. 22, 2017

Re: [Pharo-dev] XPath chapter...

by Stephane Ducasse

I do not know. querying XML is already good for me. > PS After spending significant time with other languages at work, I really > have an appreciation of how wonderful Pharo is as a development environment. This is why we should have more companies paying smart people doing cool projects in Pharo.

Oct. 22, 2017

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

by Stephane Ducasse

> > 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:. indeed. I do not get printString in String is 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? Yes this is my point. In fact I do not know what I get. So now I'm forced to type check. Stef > > > 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. 22, 2017

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

by Stephane Ducasse

Nicolas the problem is that I do not know if I will get a string or an object. the arg gets printStringed (instead of asString). Now if I want to have the correct behavior I will have to type check. Still I do not understand why printString a string wrap it 'foo' printString evaluating to 'foo' vs. 'foo' printString evaluating to '''foo''' There is something unclear to me around string representation and object representation as string. @Alistair In fact we should use displayString to call a printString for UI (list...) On Sat, Oct 21, 2017 at 10:10 PM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > 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. 22, 2017

Re: [Pharo-dev] UnifiedFFI Docs

by Esteban Lorenzano

Hi, > On 21 Oct 2017, at 21:15, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Esteban will probably reply to this thread yes, I will :) > > > 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. can you report that on fogbugz ? (along with your solution) thanks! Esteban >> >> 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. 22, 2017

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