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

[Pharo-project] SIF working - needs a small fix

by bryce＠kampjes.demon.co.uk

Bill Schwab writes: > Hello, > > I would like to tell you all the incredible things I did to get SIF > going - truth is, it loaded and just worked. The only gripe I have is > that the Pharo browsers are displaying a large number of LF or other > non-printable characters as boxes in the Pharo browsers. I have seen > Squeak do this many times, and either just ignored it or deleted them, > as my need to view the code and tolerance level allowed. It will get > old with the amount of code I plan to move. > > How would YOU fix this? Is it a SIF problem (dumping out things it > should not from Dolphin), a SIF problem (not supressing characters as > they are loaded in Pharo), or something missing in the browsers that is > expected to be fixed in Pharo? It's a line ending problem most likely. Squeak uses Mac style line endings. If there's only a few I'd delete the characters, if there's more I might try to automate it. In general automation would be a little tricky because you'd want to ignore any carriage returns in strings that you want to keep. If you know the source well enough to know that there aren't any then just write a script possibly in Squeak to remove them. It might be worthwhile trying to automatically reformat your code. That's likely to get rid of them as the RB formatter runs off the parse tree and ignores whitespace. Bryce

Oct. 1, 2008

Re: [Pharo-project] Image tidyup convention

by Igor Stasenko

2008/10/1 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Ok I saw it is below :) > I like the idea now it would be good to specify it a bit better. > I think Keith can describe it more detailed. Keith? As for me, a simple #cleanUp message added to Behavior is more than enough. Then system utils can do a cleanup by sending this message to all classes. And then , depending on implementation it does the cleanup. > Stef > > >> I would really like if Pharo will introduce a convention for tidying >> up the image, proposed by Keith. >> It could save a lot of time and nerves for developers/maintainers :) >> >> http://www.nabble.com/Squeak-low-on-space...-td13243777.html#a13244357 >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

Oct. 1, 2008

Re: [Pharo-project] Re: [build broken] 10083/10084

by StÃ©phane Ducasse

Thanks marcus ! Stef On Oct 1, 2008, at 9:15 PM, Marcus Denker wrote: > > On 01.10.2008, at 21:04, Marcus Denker wrote: > >> Please dont' update, it's broken right now. >> (And I don't have time to fix it, I have to admit) >> > > Fixed. Make sure to update to 10084, this has the compiler bug fixed. > > -- > Marcus Denker -- denker(a)iam.unibe.ch > http://www.iam.unibe.ch/~denker > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 1, 2008

Re: [Pharo-project] [updates] 10083

by Marcus Denker

On 01.10.2008, at 11:27, Simon Kirk wrote: > Not entirely fair I know, but I'm using the demo TT + PolyMorph > image which was based on 10074. If I try to update from the server > on this image it throws up an emergency debugger, which is unsavable. > Yes, this will not work. > This may well be expected, given that the TT and PolyMorph > integration isn't a standard Pharo thing yet. Are you planning to > release another TT and PolyMorph image from 10083? The problem is that this takes some effort... we should do two things: 1) integrate the TT/Polymorph in the image and 2) automate building the zip files. So: a new TT image will come, but the problem is that it all takes some time, as I do this only in my spare time.... for this week, the time is up, if I am really honest with myself. Marcus -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Oct. 1, 2008

Re: [Pharo-project] OSProcess under Pharo

by bryce＠kampjes.demon.co.uk

Bill Schwab writes: > Bryce, > > Thanks for your reply. Actually, I mentioned FFI etc. because that > appeared to be a way to get what OSProcess wanted in terms of > dependencies; using Universes should handle that part for me. > > FFI would be of interest on its own, but appears to make people > nervous. Is that for good reason? Put another way, if I want to make > some calls into a dll/so, do I really need to mess around with > creating/compiling/distributing a plugin? It seems like a lot of > overhead, especially since Dolphin does such a nice job based on a > mechanism very similar (in apperance at least) to FFI. That said, I am > interested in candid opinions; maybe things really are different in > Squeak/Pharo. FFI is fine, there's a security issue, but that's just the ability to call any dll/so in the system and so perform any action that the user is allowed to do. It's only an issue if you're running untrusted code. Bryce

Oct. 1, 2008

Re: [Pharo-project] [updates] 10083

by Marcus Denker

On 01.10.2008, at 10:53, Michael Roberts wrote: > Hi Marcus, > > good batch of changes! > > I'm just trying to understand the process by which you made these, > since I was going to make some more that are dependent on it. I > didn't see a SLICE-xx for these changes in PharoInbox, just the later > version of the individual packages in Pharo. Is this because I was > looking just at the time you published this, or did you not make a > SLICE? etc. I am just trying to follow the docs on HowToContribute. > I was putting multiple changeset into my harvesting image and then just committing the result to the repository. Right now there are three people who can do this: Stef, Adrian and me. We can harvest changesets from the bugtracker or commits from the INBOX. Marcus -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Oct. 1, 2008

[Pharo-project] Re: [build broken] 10083/10084

by Marcus Denker

On 01.10.2008, at 21:04, Marcus Denker wrote: > Please dont' update, it's broken right now. > (And I don't have time to fix it, I have to admit) > Fixed. Make sure to update to 10084, this has the compiler bug fixed. -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Oct. 1, 2008

[Pharo-project] [build broken] 10083/10084

by Marcus Denker

Please dont' update, it's broken right now. (And I don't have time to fix it, I have to admit) Marcus -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Oct. 1, 2008

Re: [Pharo-project] strange problem with 10083

by Marcus Denker

On 01.10.2008, at 20:57, Marcus Denker wrote: > > On 01.10.2008, at 20:18, StÃ©phane Ducasse wrote: > >> >> On Oct 1, 2008, at 8:00 PM, Bill Schwab wrote: >> >>> Stef, >>> >>> To reproduce, one would start with 10083 and invoke >>> >>> Installer loadOB. >>> >>> Is that correct? >> >> We found the problem :) >> some magic in bytecode generation that was broken. > > > Update 10084 fixes the problem. It recompiled the image to make > sure that no wrong method is left over. > Uhhh... and it seems to have problems recompiling the image. So that was not a fix. Marcus -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Oct. 1, 2008

Re: [Pharo-project] strange problem with 10083

by Marcus Denker

On 01.10.2008, at 20:18, StÃ©phane Ducasse wrote: > > On Oct 1, 2008, at 8:00 PM, Bill Schwab wrote: > >> Stef, >> >> To reproduce, one would start with 10083 and invoke >> >> Installer loadOB. >> >> Is that correct? > > We found the problem :) > some magic in bytecode generation that was broken. Update 10084 fixes the problem. It recompiled the image to make sure that no wrong method is left over. Marcus -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Oct. 1, 2008