Squeak-dev April 2004

squeak-dev@lists.squeakfoundation.org

172 participants
488 discussions

[VM] [Q] Closing dialog box and icon choosing
by Pavel Křivánek 05 Apr '04

05 Apr '04

Hi, when someone wants to change icon of Squeak VM (win32) he has to edit resources. The dialog box "Quit Squeak without saving" is hard coded as well. Is it possible to enter it like options in *.ini file in next versions of VMs? Thanks Pavel

1 0

Re: Your software
by editor＠squeaknews.com 05 Apr '04

05 Apr '04

Please have a look at the attached file.

1 0

update 5818
by Duane Williams 05 Apr '04

05 Apr '04

I picked up Squeak 3.7alpha-5816 from the server and tried to update it. It appears to get stuck on update 5818. How do I get past this? Thanks, Duane ___________________________________________________ Duane Thomas Williams 6514 Bartlett Street, Pittsburgh, PA 15217-1834 412-521-6227

5 5

[FIX] CollectionIsZero-dgd
by DiegoGomezDeck＠ConsultAr.com 05 Apr '04

05 Apr '04

from preamble: "Change Set: CollectionIsZero-dgd Date: 4 April 2004 Author: Diego Gomez Deck <DiegoGomezDeck(a)ConsultAr.com> Collection>>isZero completes the protocol in collection that make collections polymorphic with numbers. This also fix an error raised when Scamper is being installed in 3.7beta "!

2 1

Harvesting Party Wednesday April 7th 09:00 GMT
by Ken Causey 05 Apr '04

05 Apr '04

Just a reminder that the next Harvesting Party will take place between 09:00 (9 AM) and 13:00 (1 PM) GMT Wednesday April 7th, 2004. As usual we will meet on #squeak on irc.freenode.net. More information about the #squeak IRC channel can be found at http://people.squeakfoundation.org/article/7.html Information about the Harvesting Party idea can be found at http://people.squeakfoundation.org/article/29.html If you have the time please attend and work toward the future of Squeak. The next seven parties are scheduled for 13:00 (01:00 PM) GMT Sunday April 11, 2004 17:00 (05:00 PM) GMT Thursday April 15, 2004 21:00 (09:00 PM) GMT Monday April 19, 2004 01:00 (01:00 AM) GMT Saturday April 24, 2004 05:00 (05:00 AM) GMT Wednesday April 28, 2004 09:00 (09:00 AM) GMT Sunday May 02, 2004 13:00 (01:00 PM) GMT Thursday May 06, 2004

10 15

trying to install Morphic-Games
by Duane Williams 05 Apr '04

05 Apr '04

I tried to install Morphic-Games into Squeak3.7beta-5868 using the Package Loader. I got this message: "Error occurred during install, FloatArray>>isZero". Should I have loaded something else first? Thanks, Duane ___________________________________________________ Duane Thomas Williams 6514 Bartlett Street, Pittsburgh, PA 15217-1834 412-521-6227 Weblog: http://homepage.mac.com/duanewilliams/iblog/

2 1

LineMorph
by Ed Cavazos 05 Apr '04

05 Apr '04

I don't think I'm using the latest version of Squeak so perhaps this is no longer a problem but... Here's the from:to:color:width: method for LineMorph: ************************************************** from: startPoint to: endPoint color: lineColor width: lineWidth ^ PolygonMorph vertices: {startPoint. endPoint} color: Color black borderWidth: lineWidth borderColor: lineColor ************************************************** Shouldn't 'PolygonMorph' be changed to 'self'? This tripped me up since I subclassed LineMorph and the resulting objects weren't responding to 'isKindOf' properly... Ed _________________________________________________________________ Limited-time offer: Fast, reliable MSN 9 Dial-up Internet access FREE for 2 months! http://join.msn.com/?page=dept/dialup&pgmarket=en-us&ST=1/go/onm00200361ave…

2 1

[FIX] LineUpUpdatingMenuItems-abs
by alexstr＠actcom.net.il 05 Apr '04

05 Apr '04

"Change Set: LineUpUpdatingMenuItems-abs Date: 4 April 2004 Author: Alex Strugatsky Problem: text of UpdatingMenuItemMorth appears to be not lined up with the rest of menu items. Solution: add blank icons after updating contents of UpdatingMenuItems."

2 1

Newbie BFAV question
by Steven Swerling 05 Apr '04

05 Apr '04

I got this walkback when trying to close set of fixes that were superceded by another set of fixes. The response message is '554 <squeak-harvest(a)lists.squeakfoundation.org>: Recipient address rejected: Relay access denied'. I'm using the reply-to email address that I normally use when posting to the squeak list, and my standard smtp. I had marked the harvesting status as closed, and checked BFAV Server for the 'To:' field. I did not check any of the Review Steps items. Any idea what I'm doing wrong? TelnetProtocolError: 554 <squeak-dev(a)lists.squeakfoundation.org>: Recipient address rejected: Relay access denied 4 April 2004 4:25:10 pm VM: Win32 - a SmalltalkImage Image: Squeak3.7beta [latest update: #5868] SecurityManager state: Restricted: false FileAccess: true SocketAccess: true Working Dir D:\mywindesk\squeak\3.7 Trusted Dir D:\mywindesk\squeak\3.7\Steven Swerling Untrusted Dir C:\My Squeak\Steven Swerling [] in SMTPClient(ProtocolClient)>>checkResponse {[:response | (TelnetProtocolError protocolInstance: self) signal]} Arguments and temporary variables: response: '554 <squeak-dev(a)lists.squeakfoundation.org>: Recipient address rejec...etc... SMTPClient(ProtocolClient)>>checkResponse:onError:onWarning: Receiver: a SMTPClient Arguments and temporary variables: aResponse: '554 <squeak-dev(a)lists.squeakfoundation.org>: Recipient address reje...etc... errorBlock: [] in SMTPClient(ProtocolClient)>>checkResponse {[:response | (TelnetProtocolError protocolInstance: self) signal]}...etc... warningBlock: [] in SMTPClient(ProtocolClient)>>checkResponse {[:response | (TelnetProtocolError protocolInstance: self) signal]}...etc... Receiver's instance variables: stream: <<error during printing>> SMTPClient(ProtocolClient)>>checkResponseOnError:onWarning: Receiver: a SMTPClient Arguments and temporary variables: errorBlock: [] in SMTPClient(ProtocolClient)>>checkResponse {[:response | (TelnetProtocolError protocolInstance: self) signal]}...etc... warningBlock: [] in SMTPClient(ProtocolClient)>>checkResponse {[:response | (TelnetProtocolError protocolInstance: self) signal]}...etc... Receiver's instance variables: stream: <<error during printing>> SMTPClient(ProtocolClient)>>checkResponse Receiver: a SMTPClient Arguments and temporary variables: response: '554 <squeak-dev(a)lists.squeakfoundation.org>: Recipient address rejec...etc... Receiver's instance variables: stream: <<error during printing>> --- The full stack --- [] in SMTPClient(ProtocolClient)>>checkResponse {[:response | (TelnetProtocolError protocolInstance: self) signal]} SMTPClient(ProtocolClient)>>checkResponse:onError:onWarning: SMTPClient(ProtocolClient)>>checkResponseOnError:onWarning: SMTPClient(ProtocolClient)>>checkResponse - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - SMTPClient>>recipient: [] in SMTPClient>>mailFrom:to:text: {[:recipient | self recipient: recipient]} OrderedCollection>>do: SMTPClient>>mailFrom:to:text: [] in SMTPClient class>>deliverMailFrom:to:text:usingServer: {[smtpClient mailFrom: fromAddress to: recipientList text: messageText....]} BlockContext>>ensure: SMTPClient class>>deliverMailFrom:to:text:usingServer: MailMessage>>send DecentReviewerNotePad>>send PluggableButtonMorph>>performAction [] in PluggableButtonMorph>>mouseUp: {[:m | (m containsPoint: evt cursorPoint) ifTrue: [m performAction]]} Array(SequenceableCollection)>>do: PluggableButtonMorph>>mouseUp: PluggableButtonMorph(Morph)>>handleMouseUp: MouseButtonEvent>>sentTo: PluggableButtonMorph(Morph)>>handleEvent: PluggableButtonMorph(Morph)>>handleFocusEvent: [] in HandMorph>>sendFocusEvent:to:clear: {[ActiveHand := self. ActiveEvent := anEvent. result := focusHolder han...]} [] in PasteUpMorph>>becomeActiveDuring: {[aBlock value]} BlockContext>>on:do: PasteUpMorph>>becomeActiveDuring: HandMorph>>sendFocusEvent:to:clear: HandMorph>>sendEvent:focus:clear: HandMorph>>sendMouseEvent: HandMorph>>handleEvent: HandMorph>>processEvents [] in WorldState>>doOneCycleNowFor: {[:h | ActiveHand := h. h processEvents. capturingGesture := capturingGest...]} Array(SequenceableCollection)>>do: WorldState>>handsDo: WorldState>>doOneCycleNowFor: WorldState>>doOneCycleFor: PasteUpMorph>>doOneCycle [] in Project class>>spawnNewProcess {[[World doOneCycle. Processor yield. false] whileFalse. nil]} [] in BlockContext>>newProcess {[self value. Processor terminateActive]}

2 1

Report from a novice VM h4x0r.
by Alan Grimes 05 Apr '04

05 Apr '04

om, I've been obsessed with hacking the VM for the last 5 days or so, often staying up till 3AM watching builds compile.... I had hoped to be able to provide you with a snapshot of my progress but, unfortunately, I have hit some snags. I will describe these presently as I review the things I have learned from this excercise. My optimization plan was roughly as follows: 1. remove all unused or redundant variables and methods. 2. tune out all redundant computations. 3. use C library functions where possible (or make better use of C constructs). 4. Go through the compiler to cancel out any negative side effects from #1. 5. go through the code and re-insert variables only where necessary to reverse any regressions that couldn't be fixed by #4. I was doing okay, I made it all the way to steps 2-3 when I reached the point where my image was segfaulting or recursive erroring (with errionious instruction pointer values!) and there was no way to find what mistake I had made from the versions of the interpreter I had keept as backup for comparison. The 3.7 alpha image had too many problems to beginwith anyway. I started from scratch with a 3.6 image as a more stable base. I then inserted functions from my changes into the new image 1-by-1, comparing it to a "clean" interp.c (which I beleive to be identical to the one that I have used as my workhorse for several months now.) I went through several of these re-inclusions, running the SU test runner each time. I added a batch which caused errors, I thought "Horray! I found the bug". I was wrong. I backed out those changes and tried again, the error re-occoured. I backed out further changes from earlier versions and still got errors! Beginning to suspect foul play, I ran the test runner on the same image with my workhorse VM and was able to produce the same errors! -- I have come to the conclusion that SU test runner is very sloppy about its cleanup and exacerbates a problem deeper in the system, somewhere.... For this reason I am unable to continue untill there is some way to do an integrity check on any given image and a way to repair any corruption that may occour. =\ In the meantime, I have made a number of findings that may be of interest: 1. Many of the computations in the VM involve simple integer pointer arithmetic. I propose that instead of being addressed by only "char * memory", there be several pointers, char[] = int[] = &x which will simplify the VM code greatly... Furthermore, making all integer values word-aligned (are they already?) will tremendously improve memory access times on many architectures. 2. While the construct: | foo | foo _ self bar: baz foo = bat ifTrue: [Mars invade]. will help the inliner when bar is a non-trivial method significantly, it becomes counterproductive when bar happens to be "integerAt:" (which it is in several places) which is actually a compiler macro. 3. Many class, and a few instance variables are treated by the compiler as constants. Apparently this is a compiler hack which makes the C code more readable without affecting the binary. Unfortunately, this badly complicates the compiler class definition. Also, the C compiler does not follow the C idiom of making all constants ALLCAPS. My proposal is to edit the compiler so that it will detect degenerate methods (methods which only produce a constant value) and to treat these as constants. I beleive that this is an important change because it will allow class variables to be used by a future multithreaded interpreter which will probably require class variables such as "ActiveSmalltalkInterpreters". 4. A great many computations involve extracting bit-fields. In many cases these bit fields include important scalar information such as "sizeBits". A useful improvment would be to make these either bytes or short-ints and then let the C compiler figure out how best to extract them from the words... 5. I started experamenting with replacing long-coded block moves with calls to C's " memmove" and "memcpy" where appropriate. The motovation is that the 386 has an ungodly fast "rep movsb " compound instruction which does the operation at the speed of the FSB. It would be even better to use an inline assembly command for this but to remain portable I started trying to insert the C library calls mentioned. There are actually a number of DIFFERENT implementations of block memory copy in the VM source. One example in the Interpreter is called by a function which takes a word count then divides it by 4 to make a word coust for the method call, When it is processed by the method it is multiplied again to make the byte count used to determine the stop pointer for the For loop! 6. At many places in the VM, a whileTrue loop is used in place of a x to: y by: z do: [] loop. (it makes prettier C code.) 7. The compiler emits many unnecessary gotos. 8. The compiler will compile: foo _ foo + 1. as foo += 1, Which isn't bad code but on a non-optimizing C compiler this may turn into an add[immediate] opcode instead of the shorter inc x, opcode. 9. Both the optimizer and the interpreter have a number of implicit subclasses which are probably coded inline for performance or other reasons. These include many tables, headers, and other constructs which might be more maintainable as seperate classes. I would propose that a C calling convention be made so that message invocation such as: foo _ Bar new. foo baz. would compile as Bar_baz(); (when not inlined). 10. I came across an opcode in the interpreter whith a comment that stated it was supposed to be obsolete after 2.6!!! 11. It might be profitable to use parts of the internal smalltalk compiler in the cCode generator (if it doesn't already.) 12. One of my orrigional motives for this was the observation that certain bit-wise logic primitives on small ints will fail unnecessarily if they are stored as negative... A more general method of accessing any 32-bit int would seem to be appropriate. 13. The add opcode seems to attempt the add without changing the stack pointer and change it only after succeding. The logic operations (and some others) will change the stack pointer 3 times on success or failure! ( doing two pops followed by a push) 14. Many of the opcodes that access the stack without pushing will use the method "stackValue: 0" instead of the cleaner "stackTop". This probably won't affect the binary but it adds alot of constant arithmetic to the generated C code. It also indicates that the cCompiler relies on the native compiler too much to optimize out constant arithmetic...) 15. C99 adds a number of interesting features. Among which are improved libraries for dealing with integer types on a variety of platforms as well as new native boolean types. Squeak obviously uses sperate classes for true and false. It is not clear to me wheather there is any way to profit from this enhancement to the underlying language. C99 also adds complex math to the language. It would seem that adding primatives to take advantage of these enhancements would be of benefit. 16. C99 adds block contexts. The current cCompiler will take all inlined methods as well as loop variables and put them at the beginning of the generated function. Since any current C and even older C++ compilers will support for (int i; i < x ; i ++ ), it would be much better form to use this instead of heaping all variables at the beginning of the block. 17. The last major revision to the interpreter was 5 years ago. =\ om I am still fairly moronic with regards to matters of the interpreter but I hope that the people who have bothered to read these will find them to be of some use. Thanks for squeak!

9 23

← Newer
1
...
40
41
42
43
44
45
46
...
49
Older →

Jump to page: