- Pharo-dev - lists.pharo.org

Re: [Pharo-project] How to integrate Kernel-Extensions

by Matthew Fulmer

I know about some of these. I'll leave my comments On Wed, Oct 01, 2008 at 10:53:25PM +0200, Damien Pollet wrote: > Hi list, we (with Stef) are browsing Kernel-Extensions, here are some > notes for discussion, as we think there is stuff that should be merged > in Pharo. > > Most of the cleanup methods make sense, but what's the difference > between cleanUp and freeSomeSpace ? http://installer.pbwiki.com/FreeSomeSpace > AppRegistry class >> removeObsolete > "AppRegistry removeObsoleteClasses" > self registeredClasses copy do:[:cls| > (cls class isObsolete or:[cls isBehavior and:[cls isObsolete]]) > ifTrue:[self unregister: cls]]. > self subclasses do:[:cls| cls removeObsolete]. A cleanup method. I think I wrote it. It is used by a freeSomeSpace script > Behavior class >> flushObsoleteSubclasses > "Behavior flushObsoleteSubclasses" > ObsoleteSubclasses finalizeValues. > > Behavior >> sourceMatchesBytecodeAt: I wrote this one to make it possible to debug things that are badly compiled > Class class >> freeSomeSpace > "Fix some problems with classes. Use Smalltalk allClassesDo: since it > does not use the subclass list, which we may be modifying during this > iteration" > Smalltalk allClassesDo: [:ea | > ea fixObsoleteSuperclass. > ea removeDuplicateSubclassEntries] I wrote this one to fix some somewhat common problems that can happen in the class heiarchy, especially when unloading packages. > SystemDictionary >> globals needs to pay attention that compiled > methods share the associations > > Number >> to: stop do: aBlock displayingProgress: aString would be > probably nicer with the block argument last I wrote that one to complement #do:displayingProgress: > SequenceableCollection >> <= smells funnyâ¦ what is it useful for ? This is built to make it easy to make multi-level sort blocks for SortedCollection: aSortedCollection sortBlock: [:a :b | {a isSpecial. a name} <= {b isSpecial. b name}] > === Useless: > > ProtoObject >> iconOrThumbnailOfSize: > Object >> askFor: and askFor:ifDefault: that's a workaround > > Object >> deprecated is already here > Object >> log should be packaged in a logging package since it's a > convenience method No, that's not the idea at all. Object >> log and Null provide a very lightweight discarding logging framework. We would like it in the kernel so that no matter where a package winds up, it can always do logging, but it may be discarded. After the package Logging is loaded, the user or release team can decide where the logs go (transcript, stdout, and syslog are currently implemented) See http://wiki.squeak.org/squeak/3706 for the documentation on the logging framework. > > SequenceableCollection >> copyReplacing:with: just to type one space less ? > > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Matthew Fulmer -- http://mtfulmer.wordpress.com/

Oct. 1, 2008

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

by Bill Schwab

Bryce, It's every line of (eventually, if all goes well) several years worth of work. YIKES!! :) Speaking of the mac, does Wikipedia have it right? Did they change from CR to LF in OS-X? Do we plan a similar move? Regardless, I should be able to drop extra control characters either on the way out of Dolphin or into Pharo. Understood about inside strings; escaping them might work. RE reformatting via the RB, I realize you mean well, and therefore, please do not read even a hint of hostility into this. That said, the answer is NO WAY. Far too many times, I have been saved from myself thanks to comments dated 3-6 months apart, suggesting that something had simply not settled down and required attention. If the RB ever begins to respect pre-existing formatting, I will use it more aggressively than I do now. As it is, I use it freely for up/down moves and perhpas other miscellaneous features that do not format code. I sometimes use it on new code that has not had time to accumulate meaningful comments. Once I used Dolphin's scoped refactorings (not really refactorings at all, but useful just the same) to make sweeping changes through a couple of packages, and then manually repaired the damage; it was worth it in that case. For the above reasons, I have come to disagree with Damien about using the RB to rewrite "ClassName on:" constructs. IMHO, the resulting scattering of comments would be very poor engineering practice, especially since the class-side methods can be made to answer appropriate types w/o destroying or degrading any knowledge captured in comments. There are mentions of a magic fix for this, but every time I test the RB, it continues to mishandle comments. Thanks!! Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> bryce(a)kampjes.demon.co.uk 10/1/2008 3:50 PM >>> 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 _______________________________________________ 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] Image tidyup convention

by Matthew Fulmer

On Wed, Oct 01, 2008 at 10:53:20PM +0300, Igor Stasenko wrote: > 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? http://installer.pbwiki.com/FreeSomeSpace -- Matthew Fulmer -- http://mtfulmer.wordpress.com/

Oct. 1, 2008

[Pharo-project] How to integrate Kernel-Extensions

by Damien Pollet

Hi list, we (with Stef) are browsing Kernel-Extensions, here are some notes for discussion, as we think there is stuff that should be merged in Pharo. Null and Split-Join could be packaged on their own since they are well-defined features. Most of the cleanup methods make sense, but what's the difference between cleanUp and freeSomeSpace ? AppRegistry class >> removeObsolete "AppRegistry removeObsoleteClasses" self registeredClasses copy do:[:cls| (cls class isObsolete or:[cls isBehavior and:[cls isObsolete]]) ifTrue:[self unregister: cls]]. self subclasses do:[:cls| cls removeObsolete]. Behavior class >> flushObsoleteSubclasses "Behavior flushObsoleteSubclasses" ObsoleteSubclasses finalizeValues. Behavior >> sourceMatchesBytecodeAt: Class class >> freeSomeSpace "Fix some problems with classes. Use Smalltalk allClassesDo: since it does not use the subclass list, which we may be modifying during this iteration" Smalltalk allClassesDo: [:ea | ea fixObsoleteSuperclass. ea removeDuplicateSubclassEntries] Collection >> contains: should probably be standardized as part of the STEPS project Collection >> reject:thenDo: and select:thenDo: should be included and similar enumerations reimplemented in this way too SystemDictionary >> forgetClass: aClass logged: aBool badly named but interesting "Delete the class, aClass, from the system. Note that this doesn't do everything required to dispose of a class - to do that use Class>>removeFromSystem." aBool ifTrue: [SystemChangeNotifier uniqueInstance classRemoved: aClass fromCategory: aClass category]. SystemOrganization removeElement: aClass name. self removeFromStartUpList: aClass. self removeFromShutDownList: aClass. self removeKey: aClass name ifAbsent: []. DataStream classRemoved: aClass. self flushClassNameCache SystemDictionary >> globals needs to pay attention that compiled methods share the associations Number >> to: stop do: aBlock displayingProgress: aString would be probably nicer with the block argument last === To discuss: Collection >> removeAll: comment should explain in which cases it is useful "the slow way" ^ self removeAllSuchThat: [ :each | true ] SequenceableCollection >> <= smells funnyâ¦ what is it useful for ? SequenceableCollection >> replacing:with: replaces in place, not obvious from the name the stream methods like putOn: â¦ convenience ? are they coherent ? String >> withoutTrailing: probably makes sense but then this is mostly useful for line breaksâ¦ why not a #trimLinebreak Set >> likeOrAdd: ok but then that should be available for any collection (and renamed addIfAbsent:) "Include newObject as one of the receiver's elements, but only if not already present. Answer the oldObject." === Useless: ProtoObject >> iconOrThumbnailOfSize: Object >> askFor: and askFor:ifDefault: that's a workaround Object >> deprecated is already here Object >> log should be packaged in a logging package since it's a convenience method SequenceableCollection >> copyReplacing:with: just to type one space less ? -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Oct. 1, 2008

[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