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

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

by Keith Hodges

> #withoutTrailing: is useful for things like, knocking the end off a url or path. url withoutTrailing: $/ Keith

Oct. 1, 2008

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

by Keith Hodges

>> 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. > The idea is to promote the use of logging throughout the image using the following convention. self log <subsystem> param1: value1 param2: value2. Thus removing Transcript show: from all over the kernel, and in the process provide more control (filtering, output options etc) via the chosen logging framework. Defining Object-#log ^ Null is the easiest way of implementing a NullLogger in a minimal image. However it is expected that a normal image such as Pharo would be provided with a Transcript logger as the default option. Goran's SLLog provides Transcript, File and Syslog output. Toothpick is also supported as a backend. The other complication is that I designed the logging framework with the intention of using the ProcessSpecific package whereby each process has its own buffer for the text being logged, thus avoiding any form of blocking semaphores etc. Including ProcessSpecific in the main image is another topic for discussion. Keith

Oct. 1, 2008

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

by Keith Hodges

> 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." > > add: by convention returns the added object likeOrAdd: is primarily finding an existing object does addIfAbsent: communicate this sufficiently? Personally I think add: should return the object that is actually in the Set after the operation, whereas by default it returns the object that was potentially added. > ProtoObject >> iconOrThumbnailOfSize: > It is not useless, it enables the explorer to work with subclasses of ProtoObject, in particular MagmaProxy 's > Object >> askFor: and askFor:ifDefault: that's a workaround > Its implemented to primarily offer an alternative to adding #isThis #isThat methods to Object. Keith

Oct. 1, 2008

[Pharo-project] Cleanup - a concern

by Bill Schwab

I started Smalltalk on an educational discount copy of V-DOS, and then launched at a discounted copy of V-Win. The latter was particularly prone to crashing during a save-and-exit. To this day, I save, and then exit w/o saving. I can't get past it :) Humor aside, I would prefer to have a way to save (bloat and all), then clean, and finally see if all is happy before saving again. THEN I would exit w/o saving ;) Ideally, I would like to see such extra care supported in the IDE. 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

Oct. 1, 2008

[Pharo-project] Space tally

by Bill Schwab

Adrian, I ran the space tally, and have found, even after WARegistry clearAllHandlers. Smalltalk garbageCollect. that there are still some Seaside entrails present in the image. In particular, there are 11 instances of WAApplication, and 4 instances of WADispatcher. There are also quite a few surviving instances from the cryptography package, suggesting that I probably have some orphans from my experiments with SSL connections. I will dig around some more. It would be nice to get breakdowns by category, and I quickly ran into something that struck me as odd: is there a reason #spaceTally: answers the items and not the tally/receiver? Doing the latter would simplify slicing the results. If there is interest, I can punch it up a little and submit it for inclusion in Pharo - let me know. It won't be much, but it should be helpful in understanding what is eating up space. Thanks for calling the tally to my attention; it looks like a very useful tool. Either here or on the Pharo list (maybe both), there was some recent discussion of cleanup. IIRC, it mentioned some additional expressions to clean up Seaside; it's worth a try. I also vaguely recall some (perhaps just speculation??) mention of image growth problems with the older UI Enhancements; the image in question is months old, so that might be part of the problem. Finally, I have no baseline for how big the image should be; I just noted it was 50+MB and realized something was out of whack. I am not terribly concerned about the current image, orther than to not lose the code. I expect to build a new image once Pharo is available with PolyMorph and ideally TT integrated into the image. Depending on the timing and any deadlines that might be whooshing by, I might wait for the official release, but I am getting eager to have some of the newer refinements. 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

Oct. 1, 2008

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

by Bill Schwab

Damien, Stef, I would argue for #trimBlanks (very useful), #trimLineBreak (I do not recall needing this one, but clearl you do, so go for it), and keeping #withoutTrailing: as a separate entry point; write the others in terms of it. IIRC, #trimBlanks probably should trim leading as well as trailing nulls and spaces. The result should (of course) be a properly formatted byte string. I mention that because Dolphin uses null-terminated strings, but my recollection is that Squeak handles them more like BSTRs??? Specifically, I am NOT suggesting to reject nulls/blanks to the point of violating the storage format, only to get rid of them in the "payload." Does that make sense? 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 >>> damien.pollet(a)gmail.com 10/1/2008 3:53 PM >>> String >> withoutTrailing: probably makes sense but then this is mostly useful for line breaks* why not a #trimLinebreak

Oct. 1, 2008

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