- Pharo-dev - lists.pharo.org

Re: [Pharo-project] new Cog VMs

by mkobetic＠gmail.com

I'm probably doing something obviously wrong, but I have no luck with the Cog VM. It crashes immediately on startup even with the stock OneClick image. I downloaded the Pharo-1.1.1 OneClick images. Fetched the latest coglinux.tgz (r2340), untarred it into the pharo directory and just trying to run it from the top-level pharo directory as: coglinux/squeak Contents/Resources/pharo.image crashes immediately (with or without the -vm-display-X11 option). This is on latest Fedora 14. The old VM seems to have no problem when I try to run it the same way: Contents/Linux/squeakvm Contents/Resources/pharo.image seems to start just fine. I can copy the stack dump from the crash, but since most seem to be running fine, I suspect I'm just not doing it right. What am I missing ? Thanks, Martin "Eliot Miranda"<eliot.miranda(a)gmail.com> wrote: > there are new versions of both the SimpleStackBasedCogit and the > StackToRegisterMappingCogit Cog VMs in > VM.r2339/<http://www.mirandabanda.org/files/Cog/VM/VM.r2339/> > & VM.r2340/ <http://www.mirandabanda.org/files/Cog/VM/VM.r2340/> respectively. > These contain fixes for rounding bug causing underestimate of openPICSize > and resultant hard crashes, seen e.g. by trying to recover lost changes in a > Pharo 1.2 image installed on c:\pharo. If you're trying to reproduce Cog > crashes please upgrade to one of tthese two VMs.

Jan. 2, 2011

Re: [Pharo-project] Xtreams updates: positioning, slicing and stitching

by mkobetic＠gmail.com

"Francisco Ortiz PeÃ±aloza"<patchinko(a)gmail.com> wrote: > Hi Martin, thanks i'll try it later! > > It would help if you could provide a Metacello configuration for it. Yes, something like that is clearly needed, but I'm still finding my way around the environment. However at the moment Xtreams don't have any prerequisites, so something like the gofer expression below should do it (you can skip the tests if you want). Gofer new squeaksource: 'Xtreams'; package: 'Xtreams-VWCompatible'; package: 'Xtreams-Core'; package: 'Xtreams-Terminals'; package: 'Xtreams-Transforms'; package: 'Xtreams-Substreams'; package: 'Xtreams-SqueakExternals'; package: 'Xtreams-SqueakTextConverter'; package: 'Xtreams-CoreTests'; package: 'Xtreams-TerminalTests'; package: 'Xtreams-TransformsTests'; package: 'Xtreams-SubstreamsTests'; load But we'll likely want a metacello config eventually, especially when we bring in FFI for calling things like zlib and libcrypto. Cheers, Martin

Jan. 2, 2011

Re: [Pharo-project] Xtreams updates: positioning, slicing and stitching

by Francisco Ortiz PeÃ±aloza

Hi Martin, thanks i'll try it later! It would help if you could provide a Metacello configuration for it. Cheers, Francisco On Sat, Jan 1, 2011 at 6:03 PM, <mkobetic(a)gmail.com> wrote: > I updated the Xtreams port (http://www.squeaksource.com/Xtreams) over the > holidays to catch up with the state on VW side. The primary changes are > updates/fixes of the positioning API and a cleanup/extension of the slicing > API. The slicers are replaced by much simpler #slicing setup and the > inverse, #stitching, was added (the updated documentation can be found in > the usual place: http://code.google.com/p/xtreams/wiki/Substreams) More > details on the changes below. > > Enjoy, > > Martin > > Positioning updates: > * ++/--/+=/-=/position: now return the argument instead of self > * they all also skip as far as they can raising Incomplete with the count > of the actual amount skipped > * this means that the positioning wrapper will advance as far forward as it > needs to satisfy the request, in case of -= it means it will advance all the > way to the end of the underlying stream. > * similarly asking a positioning wrapper for length or available will make > it advance to the end > * in the other direction, positioning wrapper can't skip past the beginning > of its buffer, so if the buffer window moves forward, so does the absolute > position; position 0 is always the beginning of the buffer, whereever it is > at any given moment > * also extended ++ and -- to call the other if the argument is negative (it > helps with implementation of the others) > > All read/write/positioning calls except put:/get/read: now consistently > return element counts so that one can use a computation as an argument and > then obtain the actual number in response. This simplifies common patterns > like: > actual := [ stream ++ (x max: y) ] on: Incomplete do: [ :ex | ex > count ]. > instead of: > actual := x max: y. > [ stream ++ actual ] on: Incomplete do: [ :ex | actual := ex count > ]. > > Slicing/Stitching updates: > Replacing all the -er: slicer creation methods with the new #slicing and > adding complementary #stitching. > * #slicing is sent to a substream "prototype" and clones it when next slice > is needed, e.g. > (stream limiting: 3) slicing > * #stitching is sent to a read stream of streams and makes it look like one > continuous stream > [ stream limiting: stream get ] reading stitching > * stitching replaces the experimental proto and concatentation streams > * ReadStream>>, is now implemented with stitching too > >

Jan. 2, 2011

Re: [Pharo-project] An intuitive (or screwed) #copyFrom:

by csrabak＠bol.com.br

I would like to add to the tally. Changing Object>>copyFrom: to Object>>copyStateFrom: makes for me a lot more sense that changing (in fact by the creation of) OrderedCollection>>copyFrom: to OrderedCollection>>copyFromIndex: Except we do agree /in limine/ that OrderedCollection>>copyFrom:to: should be changed to OrederedCollection>>copyFromIndex:toEndIndex: Em 01/01/2011 17:48, Schwab,Wilhelm K < bschwab(a)anest.ufl.edu > escreveu: Lukas, I must respectfully disagree: it is also quite similar to #copyFrom:to:, and behaves *completely* differently from same. #copyFrom: really should have a more intention-revealing name. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Lukas Renggli [renggli(a)gmail.com] Sent: Saturday, January 01, 2011 2:06 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] An intuitive (or screwed) #copyFrom: Quite some software (Seaside, Mondrian, Magritte, Pier, ...) depends on the current implementation of #copyFrom:, as it is an extremely efficient way to remember and restore the state of an object: rememberReceiverDuring: aBlock previous := self shallowCopy. ^ aBlock ensure: [ self copyFrom: previous ] I don't think that the name of #copyFrom: is misleading (it derives from #copy). What you are looking for is #allButFirst: that goes along with #allButFirst, #allButLast:, allButLast, #first:, and #last:. Cheers, Lukas On 1 January 2011 19:39, Schwab,Wilhelm K wrote: > Wow. In fairness, Dolphin has one or two such oddities. IIRC, the confusion there is that external arrays (DOUBLE, DWORD, etc.) respond to #copyFrom:to: in terms of bytes, not elements. > > The problem in this case appears to be that > > 'a string with some stuff in it' copyFrom:5 > > should blow up because 5 is not a suitable source (a string of some type) from which to copy a string's state. Once it properly reports abuse, we can then move on to asking whether we want a copying selector that can be so easily confused with copying from an index. It might be better named #copyStateFrom:?? > > Sorry to beat the usual drum, but it fits: silent failures need to be hunted down and killed. > > Bill > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] > Sent: Saturday, January 01, 2011 1:29 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] An intuitive (or screwed) #copyFrom: > > HI sebastian > > If I remember correctly you are not the only one bitten by it :) so we should do something > > Object>>copyFrom: anotherObject > "Copy to myself all instance variables I have in common with anotherObject. This is dangerous because it ignores an object's control over its own inst vars. " > > Now you enumeration is too complex for me :) > >> I ask because, if so, situation goes like this: >> >> A. we think again and decide to do the right thing or we go with the alternative which is >> B. we leave it as invalid, as it is right now, and >> 1. we mislead even to smalltalkers not familiarized to squeak/pharo >> 2. we rationalize some clever way to see it as a feature even if it will mislead everybody (even ourselves in a hurry) >> 3. we lay a foundation to lightly use protocol that is typically used in collections (to do dangerous things like instVar manipulation) >> 4. we break encapsulation and manipulate extremely primitive things in a common sounding selector. >> 5. we work harder on trying to give the impression that we're leaving it like that because we're smarter than the confused people that tried to use it (proving to them that we're dumb) >> 6. we get involved in an unnecessarily complicated way of thinking that will complicate unnecessarily our future (guaranteed) >> 7. we learn how to maintain a screwed attitude in front of people trying to use intuition when using pharo >> 8. we stay comfortable (on the wrong foundation and for the wrong reasons) >> >> That would leave us with this question in the table: >> >> what is compatible with the Pharo's mission? is it A or B? > > My state of mind is always to make the world better :) > > Now > - did you check the senders to copyFrom:? > sounds ok not so many so we could deprecated it easily > > - did you check in other Smalltalk if this method is used or not? > VW not in Object but in probe something > > - did you check the ansi standard? > I guess that this is not there. > > The finder says: > 'if this isn''t broken' . 15 . 'broken' > > no single method, strange.... but indeed > 'if this isn''t broken' . 15 . 20 . 'broken' find copyFrom:to: > > Now what would be a better name > > copyFromObject: > > then > > on String>>copyFrom: ? > > Even if I would prefer (but it sucks) String>>copyFromIndex: but this is more coherent with copyFrom: index to: another > > > Stef > > > > -- Lukas Renggli www.lukas-renggli.ch

Jan. 2, 2011

Re: [Pharo-project] source.lukas-renggli.ch is down

by GermÃ¡n Arduino

Seems that it remains down still. A lot of things depending of the Lukas server are not working :( 2010/12/29 Torsten Bergmann <astares(a)gmx.de>: > and it is one of the reasons why the hudson build fails :( > > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/lastFailedBui… > > Even when Lukas restores the server it would be good to use > community controlled squeaksource servers in the future instead > of personal servers (the "truck factor" - you know) > > Bye > T. > > > -- > Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! > Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail > >

Jan. 1, 2011

Re: [Pharo-project] Graph library in Smalltalk - Need for advices

by askoh

Check out JUN for Smalltalk. http://aokilab.kyoto-su.ac.jp/jun/index.html -- View this message in context: http://forum.world.st/Graph-library-in-Smalltalk-Need-for-advices-tp3092747… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 1, 2011

Re: [Pharo-project] new Cog VMs

by Eliot Miranda

Hi All, there are new versions of both the SimpleStackBasedCogit and the StackToRegisterMappingCogit Cog VMs in VM.r2339/<http://www.mirandabanda.org/files/Cog/VM/VM.r2339/> & VM.r2340/ <http://www.mirandabanda.org/files/Cog/VM/VM.r2340/> respectively. These contain fixes for rounding bug causing underestimate of openPICSize and resultant hard crashes, seen e.g. by trying to recover lost changes in a Pharo 1.2 image installed on c:\pharo. If you're trying to reproduce Cog crashes please upgrade to one of tthese two VMs. TIA Eliot On Thu, Dec 30, 2010 at 6:02 PM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > Hi All, > > I've released a new version of Cog that has a substantially improved > code generator along the lines of Peter Deutsch's HPS (VisualWorks) and > various of Ian Piumarta's VMs. These all use a simple tecnique to identify > constant references in bytecode and to support a register-based calling > convention. While this does produce faster code it tends to accelerate > low-level code much more than high-level code as you can see by the > following benchmarks: > > SimpleStackBasedCogit: [1 to: 100000000 do: [:i|]] timeToRun 691 > StackToRegisterMappingCogit: [1 to: 100000000 do: [:i|]] timeToRun 192 > 192 - 691 / 6.91 -72% > > SimpleStackBasedCogit: 0 tinyBenchmarks '753495217 bytecodes/sec; 64769127 > sends/sec' > StackToRegisterMappingCogit: 0 tinyBenchmarks '931756141 bytecodes/sec; > 128157989 sends/sec' > 931756141 - 753495217 / 7534952.17 -24% > 128157989 - 64769127 / 647691.27 -98% > > SimpleStackBasedCogit: [Compiler recompileAll] timeToRun 47013 (no > transcript > StackToRegisterMappingCogit: [Compiler recompileAll] timeToRun 43406 (no > transcript) > 43406 - 47013 / 470.13 -7.67234594686576 > > The status of this code is essentially beta. The test suite runs the same > on the new code generator as on the old, but I think there are still bugs > because I get the occasional transient error. I am therefore very > interested in any reproducible errors you can find. > > The VMs (http://www.mirandabanda.org/files/Cog/VM/VM.r2334/) contain a few > other important changes: > > - a bug fix to bytecode<->native pc mappng that produced incorrect results > for methods containing blocks with ^-returns in them. One symptom is > incorrect highlighting of the pc in the debugger, althoguh symptoms could be > much serious. > > - jitting interpreted methods on backward branches. Currently any > interpreted method that performs more than 20 backward branches will be > considered for JIT compilation and if it is suitable (default, <= 60 > literals) will be compiled to native code. > > - new callback support. I need to commit some changes to the Alien package > to provide access to this but essentially the VM's callback support is now > able to be ported to architectures with register-based calling conventions > (ARM, PowerPC, SPARC etc). I'll try and get the Alien code released soon, > and to back-port the changes to the standard VM before the end of the > holiday. > > One thing that is still /not/ fixed is the lack of a SoundPlugin on win32. > Apologies. I'll try and get a fix for this before the end of the holidays > too, but time might be too tight. There are other priorities such as > harmonising the standard and Cog VMs for the 4.2 release. > > best > Eliot > >

Jan. 1, 2011

Re: [Pharo-project] Issue 3502 in pharo: DNU while parsing

by pharo＠googlecode.com

Updates: Cc: stephane.ducasse Labels: Milestone-1.2 Comment #1 on issue 3502 by Torsten....(a)astares.de: DNU while parsing http://code.google.com/p/pharo/issues/detail?id=3502 (No comment was entered for this change.)

Jan. 1, 2011

Re: [Pharo-project] Issue 3436 in pharo: #copyFrom: is broken

by pharo＠googlecode.com

Comment #5 on issue 3436 by rydier: #copyFrom: is broken http://code.google.com/p/pharo/issues/detail?id=3436 If we end up deprecating and reimplementing, at least make the "new" implementation in SequenceableCollection, where it can be found in STX and GnuST. I still don't think it's a good idea to add to the SequenceableCollection API though, because: - It's not ANSI (VW for instance does not have it) - There is already copyFrom:to: and allButFirst: filling the same role nearly as easy - It'll break code for no better reason than to increase readability (unless you actually look up its implementation, in which case it's quite clear what it does) - There's yet another point of difference if you want to have your code running on both Squeak and Pharo

Jan. 1, 2011

[Pharo-project] Issue 3502 in pharo: DNU while parsing

by pharo＠googlecode.com

Status: Accepted Owner: Torsten....(a)astares.de New issue 3502 by Torsten....(a)astares.de: DNU while parsing http://code.google.com/p/pharo/issues/detail?id=3502 ($A to: $Z) do: [:each | Transcript show: '|*'; show: each asString; show: '>Index: '; show: each asString; show: '*'; ] gives a cascade error in squeak and a DNU in recent Pharo: TextMorphForEditView(Object)>>doesNotUnderstand: #notify:at:in: Receiver: a TextMorphForEditView(284950528) Arguments and temporary variables: aMessage: notify: 'Cascade expected ->' at: 131 in: a ReadWriteStream '($A to: ...etc... exception: MessageNotUnderstood: TextMorphForEditView>>notify:at:in: resumeValue: nil Receiver's instance variables: bounds: 0@0 corner: 432@114 owner: a TransformMorph(182190080) submorphs: #() fullBounds: 0@0 corner: 432@114 color: Color black extension: a MorphExtension (680787968) [other: (blinkStart -> 14517886) (myDe...etc... borderWidth: 0 borderColor: Color black textStyle: a TextStyle Bitmap DejaVu Sans 9 text: a Text for '($A to: $Z) do: [:each | Transcript show: ''|*''; show: ea...etc... wrapFlag: true paragraph: a MultiNewParagraph editor: a SmalltalkEditor container: nil predecessor: nil successor: nil backgroundColor: nil margins: nil editView: a PluggableTextMorph(123469824) acceptOnCR: false Parser>>notify:at: Receiver: a Parser Arguments and temporary variables: string: 'Cascade expected' location: 131 Receiver's instance variables: source: a ReadWriteStream '($A to: $Z) do: [:each | Transcript show: ''|*''; ...etc... mark: 130 hereChar: Character arrowUp aheadChar: Character arrowUp token: #'' tokenType: #doIt currentComment: nil buffer: a WriteStream '*' typeTable: #(#xBinary #xBinary #xBinary #xBinary #xBinary #xBinary #xBinary #xB...etc... here: #']' hereType: #rightBracket hereMark: 131 hereEnd: 130 prevMark: 127 prevEnd: 127 encoder: {an EncoderForV3PlusClosures} requestor: a TextMorphForEditView(284950528) parseNode: {Transcript} failBlock: [^ failBlock value] requestorOffset: 0 tempsMark: 1 doitFlag: true properties: an AdditionalMethodState category: nil Parser>>expected: Receiver: a Parser Arguments and temporary variables: aString: 'Cascade' Receiver's instance variables: source: a ReadWriteStream '($A to: $Z) do: [:each | Transcript show: ''|*''; ...etc... mark: 130 hereChar: Character arrowUp aheadChar: Character arrowUp token: #'' tokenType: #doIt currentComment: nil buffer: a WriteStream '*' typeTable: #(#xBinary #xBinary #xBinary #xBinary #xBinary #xBinary #xBinary #xB...etc... here: #']' hereType: #rightBracket hereMark: 131 hereEnd: 130 prevMark: 127 prevEnd: 127 encoder: {an EncoderForV3PlusClosures} requestor: a TextMorphForEditView(284950528) parseNode: {Transcript} failBlock: [^ failBlock value] requestorOffset: 0 tempsMark: 1 doitFlag: true properties: an AdditionalMethodState category: nil

Jan. 1, 2011