Squeak-dev July 2004

squeak-dev@lists.squeakfoundation.org

146 participants
464 discussions

[ENH] speedup for DateAndTime>><
by Ross Boylan 03 Jul '04

03 Jul '04

The following change to DateAndTime>>< makes a noticeable difference in speed for me. Note that the version of DateAndTime I'm working with is not quite the same as the current one; I don't know if this method has changed. In words, I check if the offsets are the same, and if so, skip the asUTC conversion, which is the expensive part of the operation. Shifts in daylight savings time could cause the expensive branch to kick in. Probably the internal time should always be stored as UTC, with the offset used just for display purposes. < comparand | lutc rutc rhs| rhs _ comparand asDateAndTime. self offset == rhs offset ifTrue: [ lutc _ self utc. rutc _ rhs utc. ] ifFalse: [ lutc _ self asUTC utc. rutc _ rhs asUTC utc. ]. ^lutc first < rutc first ifTrue: [ true ] ifFalse: [ lutc first > rutc first ifTrue: [ false ] ifFalse: [ lutc second < rutc second ifTrue: [ true ] ifFalse: [ lutc second > rutc second ifTrue: [ false ] ifFalse: [ lutc third < rutc third ] ] ] ] I know this isn't a proper change set, or fileout, but my fileout from the dual change sorter seems to be broken.

1 1

Squeak Source to VW
by Marco Paga 03 Jul '04

03 Jul '04

Hi. Does anybody know a good way to port my classes from squeak to visual works. I tried to simply file in .st files, and searched the web. I found a project ( http://cvstproj.sourceforge.net/ ) that seems to be dead. Regards Marco

3 3

DateTime's and LargeIntegers
by Ross Boylan 03 Jul '04

03 Jul '04

I'm looking for ways to speed up my application, which has gotten intolerably slow. It spends a lot of its time doing operations on DateAndTime objects, which are basically Brent Pinkney's implementation of the ANSI standard for squeak. However, I see he has made some changes since the version I got. See http://minnow.cc.gatech.edu/squeak/1871 I notice that this class doesn't seem to have made it into the mainline image (3.6), though there is a TimeStamp class there. Aside from the fact that it has a different vocabulary, it doesn't have any associated concept of durations (e.g., a week), which I also need. There is at least one obvious functional difference: DateAndTime knows its offset from UTC, while TimeStamp doesn't. Not a must have feature for me. (However, I see some Mar 2004 messages with fixes, that sort of give the impression it is in the main update stream...?) My first question is if anyone could fill me in on the history of Date/Times and Durations in the image. I recall a couple of years ago there was some discussion of this, but I don't know how it turned out. In particular, there are issues of functionality, ANSI compatibility, and, as I've just discovered, speed. (DateAndTime generally converts stuff to a large integer and then operates; TimeStamp does not, at least in the < operator, which is eating a lot of my time). I also recall there was another change set being bandied about that introduced ANSI compatibility into the image. That had a different Date/Time implementation. Details at http://minnow.cc.gatech.edu/squeak/2384 Second, I see some discussion of LargeInteger plugins. That might make my operations go much faster. Are those builtin by default? I don't see anything in /usr/lib/squeak, even for the 3.6 Debianized vm that I got, I think, from Ned Konz. Would such a plugin help? How do I get or build it? How do I know if I'm already using it? To give you a sense of why I care, here are some timings in the profiler as I add a single task to my tasklist: The first column is time in seconds (not ms) 43 LargeNegativeInteger>>quo: 21 SmallInteger>>* 18 LargePositiveInteger>>asFloat 14 LargePositiveInteger>>+ That's a total of 68% of total execution time right there. Overall, the operations spends 64% of its time in the main morphic loop, within which 19% operations on DateAndTime or Durations 36% evaluating a sort block, within which 35% (i.e., almost all) operations on DateAndTime Obviously, waiting over a minute to add a task is far from user friendly! (Athlon 800Mhz). There is also the possibility of making it do fewer of these operations to begin with, but if there's a quick way to get a speed up that would be great.

6 11

The future is coming ...
by Serge Stinckwich 02 Jul '04

02 Jul '04

... here : http://atsosxdev.doit.wisc.edu/croquetdevelopment/ -- oooo Serge Stinckwich OOOOOOOO Université de Caen>CNRS UMR 6072>GREYC>MAD OOESUGOO http://purl.org/net/SergeStinckwich oooooo Smalltalkers do: [:it | All with: Class, (And love: it)] \ / ##

1 0

REMINDER: Harvesting Party Saturday July 3rd 21:00 GMT
by Ken Causey 02 Jul '04

02 Jul '04

Just a reminder that the next Harvesting Party will take place between 21:00 (9 PM) GMT Saturday July 3rd and 01:00 (1 AM) GMT Sunday July 4th, 2004. As usual we will meet in #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 01:00 (01:00 AM) GMT Thursday July 08, 2004 05:00 (05:00 AM) GMT Monday July 12, 2004 09:00 (09:00 AM) GMT Friday July 16, 2004 13:00 (01:00 PM) GMT Tuesday July 20, 2004 17:00 (05:00 PM) GMT Saturday July 24, 2004 21:00 (09:00 PM) GMT Wednesday July 28, 2004 01:00 (01:00 AM) GMT Monday August 02, 2004

1 0

[FIX][BUG]RuleDate>>basicUpdateForMonth:year: - source fails to compile ( It looks different because classes were just changed recently )
by jp1660＠att.net 02 Jul '04

02 Jul '04

It looks different because classes were just changed recently. If you go back to 3.6, you'll see how the RuleDate class fit into the rest of the structure. I haven't reviewed your changes just yet, but I'll check them out. I've been researching the class in my spare time for about a month.

1 0

[UPDATES] 2 for Squeak3.7beta
by dway＠mailcan.com 02 Jul '04

02 Jul '04

A couple more semi-essential fixes before 3.7gamma. Including removal of String>>asPlural, by popular demand. - Doug ------------------------------ 5968EnsureEssentialProcs-nk -- Ned Konz -- 21 June 2004 It's possible to kill off the WeakArray finalization process, and it never gets restarted. This can cause many hard-to-diagnose problems. This change set ensures that the WeakArray finalization process is started at every start up. It also shuts down the EventSensor's interruptWatcherProcess and eventTicklerProcess at shutdown time (and starts them at startUp time, of course). (Removed InputSensor class>>startUp from original changeset which was not needed. -dew) 5969asPluralRemoval -- Yoshiki Ohshima -- 29 June 2004 Remove asPlural." <This automated message brought to you by the UpdateIncorporationTool.> <See the UpdateIncorporationTool package on SqueakMap for details.>

1 0

Re: [BUG][FIX] MailMessage with multiple to headers
by Doug Way 02 Jul '04

02 Jul '04

MailMessage is definitely in need of some help. Most annoying is that there are getters/accessors for "to", "cc" and other commonly used fields, but no setters... you have to call setField:/setFields: with a hardcoded 'to' string, etc. Maybe this should just be cleaned up in 3.8. Although this changeset is a reasonable first step. (Except it's missing the test class definition for some reason.) - Doug On Tuesday, June 29, 2004, at 10:39 AM, frank.shearar(a)rnid.org.uk wrote: > > "Change Set: MailMessageTo-fbs > Date: 29 June 2004 > Author: Frank Shearar > > Currently MailMessage allows all sorts of undesirable occurences, like > allowing multiple To lines. RFC 2822 forbids this. This changeset > supplies a protocol that, if used, guarantees that you can add as many > recipients as you like to a MailMessage while maintaining a single To > header. > > Too, this changeset moves MailMessage to the Network-RFC822-Tests > category." > <MailMessageTo-fbs.cs.gz>

1 0

Magma counseling
by Ramiro Diaz Trepat 02 Jul '04

02 Jul '04

Does anybody have a more detailed guide or code examples on using Magma than what is on the main Squeak Swiki? I am running into problems, at a very eary stage, and I am almost sure that these problems are caused because of my meager knowledge on how to use the framework. For example, all the collections held as attributes by classes that you intend to persist should be MagmaCollections? How does the fact of using Magma affect the code and development process? What are the most important things to keep in mind? -- Ramiro Díaz Trepat http://neosmt.com

3 5

[ENH] SetInspector
by keelerp＠cse.ogi.edu 02 Jul '04

02 Jul '04

from preamble:

1 0

Jump to page: