Squeak-dev February 2012

squeak-dev@lists.squeakfoundation.org

62 participants
155 discussions

The Inbox: Kernel-cmm.670.mcz
by commits＠source.squeak.org 05 Feb '12

05 Feb '12

A new version of Kernel was added to project The Inbox: http://source.squeak.org/inbox/Kernel-cmm.670.mcz ==================== Summary ==================== Name: Kernel-cmm.670 Author: cmm Time: 5 February 2012, 2:32:50.946 pm UUID: b6408357-975c-4212-93c5-7932cc175306 Ancestors: Kernel-cmm.669 Perform initialization required for prior change in the postscript. =============== Diff against Kernel-cmm.669 =============== Item was changed: + (PackageInfo named: 'Kernel') postscript: 'DateAndTime classPool at: #OffsetsAreValid put: true. + Timespan withAllSubclassesDo: [ : each | each initialize ]'! - (PackageInfo named: 'Kernel') postscript: 'DateAndTime classPool at: #OffsetsAreValid put: true'!

1 0

Re: [squeak-dev] About the new Date
by Chris Muller 05 Feb '12

05 Feb '12

Hi Dave, thanks for the feedback. However, the yet-another-class cannot actually satisfy my needs because I also require globalized Minute, Hour, Month, Quarter and Year timespans. I totally understand and appreciate what you are saying about having a "lean Date" a-la Squeak 3.6. Would you please look at the attached packages? This package goes back to 2004, prior to the existence of Chronology. It wraps a single LargeInteger to represent any point-in-time precise to the millisecond. In fact, observe version 44 of the package even went a step further and, rather than wrapping an Integer, it even *inherited* from Integer -- e.g., each MaDate WAS an Integer, with only behaviours. Guess what: It didn't perform any better than Chronology's 3 SmallIntegers. (The benchmark results are published in the version comments of the attached packages, check it out). Also, it created unnecessary converting complexities since there are other areas of the system that use the standard Chronology class. The other problem is: If we bring in yet-more-classes, where does that leave Date, et al? They're still horribly broken, as you said in your prior message. Unsuspecting Squeakers all over the world can be drastically affected by this. This is not just my problem, it's Squeak's problem, and it's a doozie -- wouldn't you say? The solution in the Inbox addresses all of the practical issues whilst retaining a single, consistent, coherent and correct implementation of time-objects for Squeak. It does not break Chronology. Dave, I've been deep down this road and have spent a LOT of time and effort to address it. I grok the issues to the core and the solution in the Inbox addresses them in the safest and smoothest way possible -- without duplication. Please let us move forward. I ask you to give the Inbox solution a try. - Chris Please find, attached, the package "Ma time objects". > Hi Chris, > I am leaning towards the "yet another class" approach. In the abstract, > because I think we are dealing with two different kinds of thing here, > and that would justify two classes. But in the concrete, and more > specifically with respect to the Date hash performance problem and > the time zone problem, here is why: > > If I look at what you did in the inbox for Date, you basically are > normalizing the offset from UTC in specifying the start time of > date. The duration of the date object is of no interest to you, so > you could (for your application) get rid of the duration instance > variable. Now if you look at the start time, it is a DateAndTime > with all instance variables zeroed out except for jdn. Thus the > only instance variable data in your Date object that carries any > useful information is the jdn, which is just a SmallInteger. > > This suggests that if you get rid of all the instance variables > that carry no information, what you are left with is a Date object > with a single instance variable for julianDayNumber. This would > be extremely fast and efficient for hashing and comparison, and > the meaning if this object could be understood with no confusion > regarding time spans, time zones, or durations. If you could have > a date object like this, it might very well solve your problems > with performance and timezone ambiguities. > > The interesting thing about this is that the stripped-down date > object that I am describing here is pretty much exactly the same > as the Date that was implemented in Squeak prior to Chronology > (i.e. in Squeak 3.6 and earlier). So if it turns out that the > Squeak 3.6 implementation of Date solves the performance and > timezone problems for applications like yours, then I think we > would be perfectly justified in adding another class to the system. > > I work with manufacturing systems in which I run into the concept > of a "scheduled production date". This sort of date has nothing > to do with durations, and very little to do with any actual point > in time. For example, a vehicle may be schedule to be manufactured > on a production date, and I want to be able to do things like find > the list of vehicles to be produced on a production date, or identify > parts and material supplies associated with that production date. But > I do not care if that "date" is 24 hours in duration, and I do not > care what hour of the day the scheduled production date begins on. > > I don't know if this is similar to the kinds of date you encounter > in a financial application, but I am envisioning financial transactions > being associated with a "transaction date" or something of that nature, > and I suspect this may be similar in some ways to the idea of a > "scheduled production date". If so, these are things that could be > very efficiently represented by a date object based on julian day > number, as opposed to the far more complicated representation of > date as a DateAndTime with Duration as found in Squeak today. > > Dave >

2 1

Re: [squeak-dev] Re: Trying to undeerstand Morphic subclasses and step/stepAt:
by Dave Mason 05 Feb '12

05 Feb '12

On 2012-Feb-5, at 7:40 , Bob Arning wrote: > Look at the methods #wantsSteps. Bingo! I assumed it was something stupid I was missing. On 2012-Feb-4, at 14:23 , Sean P. DeNigris wrote: > I don't know if it's any better, but when I create my own morph-in-a-window, > I usually don't subclass SystemWindow, but add my morph to a window using > openInWindowLabelled: or addMorph:fullFrame:. I feel like I have a little > more flexibility if I later want to use it not-in-a-window. After defining wantsSteos, I see that color: seems to work a bit strangely too in SystemWindow, so I'm going to try this. Thanks, Bob and Sean.

2 3

Trying to undeerstand Morphic subclasses and step/stepAt:
by Dave Mason 05 Feb '12

05 Feb '12

Hi, I want to build a morphic application (for algorithm animation) so I need to do something in the step method. I wanted to make it a subclass of SystemWindow (I'd actually prefer StandardWindow in Pharo but there doesn't appear to be an equivalent in Squeak). But when I do, the step method doesn't get called. (Nor does stepAt:) (And StandardWindow behaves the same.). But if I move it to MorphicModel step/stepAt: gets called, but I don't get any of that SystemWindow goodness. I've looked at the dispatch in Morph, and I don't see anything different in Worldstate>>runLocalStepMethodIn: but this stuff is very difficult to debug, because there's asynchronous stuff running behind the scenes. In particular, lastStepMessage value: now. lastStepMessage ifNotNil: [... is a little weird! Any pointers appreciated. Thanks ../Dave

3 3

Daily Commit Log
by commits＠source.squeak.org 05 Feb '12

05 Feb '12

Changes to Trunk (http://source.squeak.org/trunk.html) in the last 24 hours: http://lists.squeakfoundation.org/pipermail/packages/2012-February/005184.h… Name: Kernel-cmm.669 Ancestors: Kernel-eem.668 Introduced Timespan class>>defaultOffset. This is the offset that will be used for creation of all Timespans when an offset is not specified. When an offset is specified or involved in construction or calculation, the result is now produced in terms of the source offset. For example, Date today now produces a globalized date by default. However, "Date starting: (DateAndTime year: 2004 month: 2 day: 29 hour: 13 minute: 33 second: 0 offset: 2 hours)" produces a Date.whose start is expressed in terms of UTC+2. The default defaultOffset is Duration zero so that Squeak will have fast, globalized Dates out of the box. Globalized Dates are common for applications. Legacy localized Dates can be obtained by evaluating "Date localize" so that, when an offset is not specified or otherwise involved in the input, the local offset will be used. ============================================= http://lists.squeakfoundation.org/pipermail/packages/2012-February/005185.h… Name: ReleaseBuilder-cmm.76 Ancestors: ReleaseBuilder-cmm.75 - Register TTC fonts for next build. - Adjust the standard window size to tall rather than wide. =============================================

1 0

The Trunk: ReleaseBuilder-cmm.76.mcz
by commits＠source.squeak.org 04 Feb '12

04 Feb '12

Chris Muller uploaded a new version of ReleaseBuilder to project The Trunk: http://source.squeak.org/trunk/ReleaseBuilder-cmm.76.mcz ==================== Summary ==================== Name: ReleaseBuilder-cmm.76 Author: cmm Time: 4 February 2012, 3:01:58.442 pm UUID: 44968a0b-5f3e-4056-b591-8c3b720d02e8 Ancestors: ReleaseBuilder-cmm.75 - Register TTC fonts for next build. - Adjust the standard window size to tall rather than wide. =============== Diff against ReleaseBuilder-cmm.75 =============== Item was changed: ----- Method: ReleaseBuilderTrunk class>>prepareNewBuild (in category 'scripts') ----- prepareNewBuild "ReleaseBuilderTrunk prepareNewBuild" "Prepare everything that should be done for a new image build" + TTCFont registerAll. + RealEstateAgent standardSize: 400@500. SystemVersion setVersion. SMLoaderPlus setDefaultFilters: (OrderedCollection with: #filterSafelyAvailable). self setDisplayExtent: 800 @ 600; setPreferences; switchTo43Repository; openWelcomeWorkspaces. "Make DependencyBrowser accessible on the open menu." DependencyBrowser initialize. Smalltalk cleanUp: true. Undeclared removeUnreferencedKeys. Smalltalk garbageCollect!

1 0

How to have a fast and usable Date? (was: new Bug in Locale)
by Chris Muller 04 Feb '12

04 Feb '12

> When you execute "Date today", it produces a Date object with DateAndTime > localTimeZone's offset Jon, I'm very curious your thoughts about this -- that a Date needs to know its timezone. By Date today being a special, localized instance of today, it means February 1st, 2012 created in other timezones or maybe even since a daylight-savings cutover, are now not equal. Worse, the hashing cost: |dt| dt:=Date today. [ dt hash ] bench '108,000 per second.' |dt| dt:=Date today makeUTC. [ dt hash ] bench '1,360,000 per second.' Squeak users all over the world except in UTC are using slow Dates. You can bet they probably don't expect them to be time-zone sensitive. That would be what a DateAndTime would be for. I have more than one of my own applications which use Dates, but none of them are interested in the timezone of the midnight those dates "started" at. But, due to that hashing cost, I'm forced to sprinkle the code with #makeUTC calls (just checked: I'm up to 13 senders now!) just so that regular comparing and arithmetic operations will behave correctly. There are plenty of use-cases where applications employ Dates do not want want them to be TZ-specific. But is there any use case anywhere where timezone-specific Dates would be more useful and/or more efficient than just a DateAndTime? I tried to make this case once before, http://lists.squeakfoundation.org/pipermail/squeak-dev/2011-July/160571.html but no one had any concrete context of their own to be able to relate. But you just did, and I wondered whether you had any thoughts.. On Tue, Jan 31, 2012 at 10:12 AM, Jon Hylands <jon(a)huv.com> wrote: > > Hi everyone, > > I've ported some of my code into Squeak 4.3 (was running in 4.2 before), and > ran into a weird issue comparing Date objects. > > When you execute "Date today", it produces a Date object with DateAndTime > localTimeZone's offset, which is set upon image startup to be Locale >> > offsetLocalToUTC, which in turn calls Locale >> primTimezone. > > On a 4.2 image, on both my XP and Windows 7 machines, that primitive returns > -300 (minutes), which is -5 hours, which is correct (since I live in SW > Ontario, Canada, which is EST). > > On a 4.3 image, with or without updates, that method returns -240, which is > -4, which is clearly wrong at this point in time. > > - Jon > > > >

6 16

The Inbox: KernelTests-cmm.214.mcz
by commits＠source.squeak.org 04 Feb '12

04 Feb '12

A new version of KernelTests was added to project The Inbox: http://source.squeak.org/inbox/KernelTests-cmm.214.mcz ==================== Summary ==================== Name: KernelTests-cmm.214 Author: cmm Time: 3 February 2012, 6:38:24.812 pm UUID: 23ae3769-73c1-4ec4-b843-927b235b3a6f Ancestors: KernelTests-ul.213 - Tests updated for globalized Timespans. =============== Diff against KernelTests-ul.213 =============== Item was changed: ----- Method: DateAndTimeLeapTest>>setUp (in category 'running') ----- setUp localTimeZoneToRestore := DateAndTime localTimeZone. DateAndTime localTimeZone: TimeZone default. aDateAndTime := (DateAndTime year: 2004 month: 2 day: 29 hour: 13 minute: 33 second: 0 offset: 2 hours). aTimeZone := TimeZone default. + aDuration := Duration days: 0 hours: 13 minutes: 33 seconds: 0 nanoSeconds: 0. + Timespan withAllSubclasses do: [ : each | each localize ]! - aDuration := Duration days: 0 hours: 13 minutes: 33 seconds: 0 nanoSeconds: 0 - ! Item was changed: ----- Method: DateAndTimeLeapTest>>tearDown (in category 'running') ----- tearDown + DateAndTime localTimeZone: localTimeZoneToRestore. + Timespan withAllSubclassesDo: [ : each | each globalize ]! - DateAndTime localTimeZone: localTimeZoneToRestore. - "wish I could remove the time zones I added earlier, tut there is no method for that" - ! Item was changed: ----- Method: DateAndTimeLeapTest>>testAsDate (in category 'testing') ----- testAsDate + self assert: (aDateAndTime offset: DateAndTime localTimeZone offset) asDate = 'February 29, 2004' asDate! - self assert: aDateAndTime asDate = 'February 29, 2004' asDate. - - ! Item was changed: ----- Method: DateAndTimeLeapTest>>testAsMonth (in category 'testing') ----- testAsMonth + self assert: + (aDateAndTime offset: Month defaultOffset) asMonth = + (Month + month: 'February' + year: 2004)! - self assert: aDateAndTime asMonth = (Month month: 'February' year: 2004). - ! Item was changed: ----- Method: DateAndTimeLeapTest>>testAsSeconds (in category 'testing') ----- testAsSeconds + self assert: aDuration asSeconds = 48780. + self assert: aDateAndTime asSeconds = 3255514380! - self assert: aDuration asSeconds = 48780. - self assert: aDateAndTime asSeconds = 3255507180 - - ! Item was changed: ----- Method: DateAndTimeLeapTest>>testAsWeek (in category 'testing') ----- testAsWeek + self assert: (aDateAndTime offset: DateAndTime localTimeZone offset) asWeek = (Week starting: '02-29-2004' asDate)! - self assert: aDateAndTime asWeek = (Week starting: '02-29-2004' asDate). - ! Item was changed: ----- Method: DateAndTimeLeapTest>>testAsYear (in category 'testing') ----- testAsYear + | year | + year := (aDateAndTime offset: DateAndTime localTimeZone offset) asYear. + self assert: year = (Year starting: '02-29-2004' asDate). + self deny: year = (Year starting: '01-01-2004' asDate)! - self assert: aDateAndTime asYear = (Year starting: '02-29-2004' asDate). - self deny: aDateAndTime asYear = (Year starting: '01-01-2004' asDate) - ! Item was changed: ----- Method: DateAndTimeLeapTest>>testMidnight (in category 'testing') ----- testMidnight + | midnight | + midnight := (aDateAndTime offset: DateAndTime localTimeZone offset) midnight. + self assert: midnight = '2004-02-29T00:00:00+00:00' asDateAndTime. + self deny: midnight = '2004-02-29T00:00:00+02:00' asDateAndTime! - self assert: aDateAndTime midnight = '2004-02-29T00:00:00+00:00' asDateAndTime. - self deny: aDateAndTime midnight = '2004-02-29T00:00:00+02:00' asDateAndTime - ! Item was changed: ----- Method: DateTest>>testStarting (in category 'testing') ----- testStarting + self assert: aDate = (Date starting: ((DateAndTime fromString: '2004-01-23T12:12') offset: Date defaultOffset))! - self assert: aDate = (Date starting: (DateAndTime fromString: '2004-01-23T12:12')). ! Item was changed: ----- Method: TimeStampTest>>testAccessing (in category 'Tests') ----- testAccessing | d t | d := '1-10-2000' asDate. t := '11:55:00 am' asTime. self + assert: (timestamp offset: Date defaultOffset) date = d; + assert: (timestamp offset: Date defaultOffset) time = t. - assert: timestamp date = d; - assert: timestamp time = t. ! Item was changed: ----- Method: YearTest>>testCurrent (in category 'Tests') ----- testCurrent + self assert: + Year current start = + ((DateAndTime + year: DateAndTime now year + month: 1 + day: 1) offset: Year defaultOffset)! - - | yyyy | - - yyyy := DateAndTime now year. - - self assert: Year current start = (DateAndTime year: yyyy month: 1 day: 1)!

1 0

unintended trunk commit
by Chris Muller 04 Feb '12

04 Feb '12

Darn! I meant that to go to Inbox -- I had compared against trunk to get the differences but forgot to go back to MC browser and select Inbox before I hit the button..

1 1

The Inbox: Kernel-cmm.669.mcz
by commits＠source.squeak.org 04 Feb '12

04 Feb '12

A new version of Kernel was added to project The Inbox: http://source.squeak.org/inbox/Kernel-cmm.669.mcz ==================== Summary ==================== Name: Kernel-cmm.669 Author: cmm Time: 3 February 2012, 5:55:11.175 pm UUID: 5ddec343-01ad-4e76-b32c-299fac68ec09 Ancestors: Kernel-eem.668 Introduced Timespan class>>defaultOffset. This is the offset that will be used for creation of all Timespans when an offset is not specified. When an offset is specified or involved in construction or calculation, the result is now produced in terms of the source offset. For example, Date today now produces a globalized date by default. However, "Date starting: (DateAndTime year: 2004 month: 2 day: 29 hour: 13 minute: 33 second: 0 offset: 2 hours)" produces a Date.whose start is expressed in terms of UTC+2. The default defaultOffset is Duration zero so that Squeak will have fast, globalized Dates out of the box. Globalized Dates are common for applications. Legacy localized Dates can be obtained by evaluating "Date localize" so that, when an offset is not specified or otherwise involved in the input, the local offset will be used. =============== Diff against Kernel-eem.668 =============== Item was changed: Timespan subclass: #Date instanceVariableNames: '' classVariableNames: '' poolDictionaries: 'ChronologyConstants' category: 'Kernel-Chronology'! + !Date commentStamp: 'cmm 2/3/2012 17:30' prior: 0! - !Date commentStamp: '<historical>' prior: 0! Instances of Date are Timespans with duration of 1 day. + + Their default creation assumes a start of midnight of UTC to provide the fast, globalized Dates out of the box. The legacy behavior that creates Timezone-sensitive Dates can be used by sending #localizedDates. + ! - Their default creation assumes a start of midnight in the local time zone.! Item was changed: ----- Method: Date class>>julianDayNumber: (in category 'squeak protocol') ----- + julianDayNumber: aJulianDayNumber + ^ self starting: + (DateAndTime + julianDayNumber: aJulianDayNumber + offset: self defaultOffset)! - julianDayNumber: aJulianDayNumber - - ^ self starting: (DateAndTime julianDayNumber: aJulianDayNumber)! Item was changed: ----- Method: Date class>>starting: (in category 'squeak protocol') ----- starting: aDateAndTime + ^ self - ^ super starting: aDateAndTime midnight duration: Duration oneDay! Item was changed: ----- Method: Date class>>year:day: (in category 'squeak protocol') ----- + year: year day: dayOfYear + ^ self starting: + (DateAndTime + year: year + day: dayOfYear + hour: 0 + minute: 0 + second: 0 + offset: self defaultOffset)! - year: year day: dayOfYear - - ^ self starting: (DateAndTime year: year day: dayOfYear) - ! Item was changed: ----- Method: Date class>>year:month:day: (in category 'squeak protocol') ----- + year: year month: month day: day + ^ self starting: + (DateAndTime + year: year + month: month + day: day + hour: 0 + minute: 0 + second: 0 + offset: self defaultOffset)! - year: year month: month day: day - - ^ self starting: (DateAndTime year: year month: month day: day)! Item was changed: ----- Method: DateAndTime class>>julianDayNumber: (in category 'squeak protocol') ----- + julianDayNumber: anInteger + ^ self + julianDayNumber: anInteger + offset: self localOffset! - julianDayNumber: aJulianDayNumber - - ^ self basicNew - ticks: aJulianDayNumber days ticks offset: self localOffset; - yourself! Item was added: + ----- Method: DateAndTime class>>julianDayNumber:offset: (in category 'squeak protocol') ----- + julianDayNumber: anInteger offset: aDuration + ^ self basicNew + ticks: anInteger days ticks + offset: aDuration ; + yourself! Item was changed: ----- Method: DateAndTime class>>now (in category 'ansi protocol') ----- now + ^ self nowWithOffset: self localOffset! - | nanoTicks msm | - - nanoTicks := (msm := self milliSecondsSinceMidnight) * 1000000. - - (LastTick < nanoTicks) ifTrue: [ - LastTick := nanoTicks. - ^ self todayAtMilliSeconds: msm]. - - LastTickSemaphore critical: [ - LastTick := LastTick + 1. - ^ self todayAtNanoSeconds: LastTick] - - " - [ 10000 timesRepeat: [ self now. ] ] timeToRun / 10000.0 . - - If calls to DateAndTime-c-#now are within a single millisecond the semaphore code - to ensure that (self now <= self now) slows things down considerably by a factor of about 20. - - The actual speed of a single call to DateAndTime-now in milliseconds is - demonstrated by the unguarded method below. - - [ 100000 timesRepeat: [ self todayAtMilliSeconds: (self milliSecondsSinceMidnight) ] ] timeToRun / 100000.0 . 0.00494 0.00481 0.00492 0.00495 - - "! Item was added: + ----- Method: DateAndTime class>>nowWithOffset: (in category 'squeak protocol') ----- + nowWithOffset: aDuration + | nanoTicks msm | + + nanoTicks := (msm := self milliSecondsSinceMidnight) * 1000000. + + (LastTick < nanoTicks) ifTrue: [ + LastTick := nanoTicks. + ^ self todayAtMilliSeconds: msm offset: aDuration]. + + LastTickSemaphore critical: [ + LastTick := LastTick + 1. + ^ self todayAtNanoSeconds: LastTick offset: aDuration] + + " + [ 10000 timesRepeat: [ self now. ] ] timeToRun / 10000.0 . + + If calls to DateAndTime-c-#now are within a single millisecond the semaphore code + to ensure that (self now <= self now) slows things down considerably by a factor of about 20. + + The actual speed of a single call to DateAndTime-now in milliseconds is + demonstrated by the unguarded method below. + + [ 100000 timesRepeat: [ self todayAtMilliSeconds: (self milliSecondsSinceMidnight) ] ] timeToRun / 100000.0 . 0.00494 0.00481 0.00492 0.00495 + + "! Item was changed: ----- Method: DateAndTime class>>todayAtMilliSeconds: (in category 'squeak protocol') ----- + todayAtMilliSeconds: milliSecondsSinceMidnight + self deprecated: 'Use todayAtMilliSeconds:offset:.'. + ^ self + todayAtMilliSeconds: milliSecondsSinceMidnight + offset: self localOffset! - todayAtMilliSeconds: milliSecondsSinceMidnight - - "This is usually only during system startup..." - self waitForOffsets. - - ^ self basicNew - setJdn: DaysSinceEpoch - seconds: (milliSecondsSinceMidnight // 1000) - nano: (milliSecondsSinceMidnight \\ 1000 * 1000000 ) - offset: self localOffset - - " - [ 100000 timesRepeat: [ self fromMilliSeconds: self milliSecondsSinceMidnight. ] ] timeToRun. - "! Item was added: + ----- Method: DateAndTime class>>todayAtMilliSeconds:offset: (in category 'squeak protocol') ----- + todayAtMilliSeconds: milliSecondsSinceMidnight offset: aDuration + + "This is usually only during system startup..." + self waitForOffsets. + + ^ self basicNew + setJdn: DaysSinceEpoch + seconds: (milliSecondsSinceMidnight // 1000) + nano: (milliSecondsSinceMidnight \\ 1000 * 1000000 ) + offset: aDuration + + " + [ 100000 timesRepeat: [ self fromMilliSeconds: self milliSecondsSinceMidnight. ] ] timeToRun. + "! Item was changed: ----- Method: DateAndTime class>>todayAtNanoSeconds: (in category 'squeak protocol') ----- + todayAtNanoSeconds: nanoSecondsSinceMidnight + self deprecated: 'Use todayAtNanoSeconds:offset:.'. + self + todayAtNanoSeconds: nanoSecondsSinceMidnight + offset: self localOffset! - todayAtNanoSeconds: nanoSecondsSinceMidnight - - "This is usually only during system startup..." - self waitForOffsets. - - ^ self basicNew - setJdn: DaysSinceEpoch - seconds: (nanoSecondsSinceMidnight // 1000000000) - nano: (nanoSecondsSinceMidnight \\ 1000000000 ) - offset: self localOffset - ! Item was added: + ----- Method: DateAndTime class>>todayAtNanoSeconds:offset: (in category 'squeak protocol') ----- + todayAtNanoSeconds: nanoSecondsSinceMidnight offset: aDuration + + "This is usually only during system startup..." + self waitForOffsets. + + ^ self basicNew + setJdn: DaysSinceEpoch + seconds: (nanoSecondsSinceMidnight // 1000000000) + nano: (nanoSecondsSinceMidnight \\ 1000000000 ) + offset: self localOffset + ! Item was changed: ----- Method: DateAndTime>>asSeconds (in category 'smalltalk-80') ----- asSeconds "Return the number of seconds since the Squeak epoch" + ^ (self - (self class epoch offset: offset)) asSeconds! - - ^ (self - (self class epoch)) asSeconds! Item was changed: ----- Method: DateAndTime>>makeUTC (in category 'squeak protocol') ----- makeUTC + "Make the receiver's timezone UTC." - "Change the receiver's timezone to UTC. Like #asUTC, but modifies the receiver and is much faster." self primOffset: Duration zero! Item was changed: ----- Method: DateAndTime>>midnight (in category 'squeak protocol') ----- midnight + "Answer a DateAndTime starting at midnight of the same timezone offset as the receiver." + ^ self class basicNew - "Answer a DateAndTime starting at midnight local time" - - ^self class basicNew setJdn: jdn seconds: 0 nano: 0 + offset: offset! - offset: self class localOffset - ! Item was changed: ----- Method: Month class>>month:year: (in category 'squeak protocol') ----- + month: month year: year - month: month year: year "Create a Month for the given <year> and <month>. <month> may be a number or a String with the name of the month. <year> should be with 4 digits." + ^ self starting: + (DateAndTime + year: year + month: month + day: 1 + hour: 0 + minute: 0 + second: 0 + offset: self defaultOffset)! - - ^ self starting: (DateAndTime year: year month: month day: 1) - ! Item was changed: ----- Method: Month class>>starting:duration: (in category 'squeak protocol') ----- starting: aDateAndTime duration: aDuration "Override - a each month has a defined duration" | start adjusted days | start := aDateAndTime asDateAndTime. adjusted := DateAndTime + year: start year + month: start month + day: 1 + hour: 0 + minute: 0 + second: 0 + offset: start offset. + days := self + daysInMonth: adjusted month + forYear: adjusted year. - year: start year - month: start month - day: 1. - days := self daysInMonth: adjusted month forYear: adjusted year. ^ super starting: adjusted + duration: (Duration days: days)! - duration: (Duration days: days) - ! Item was changed: Magnitude subclass: #Timespan instanceVariableNames: 'start duration' classVariableNames: '' poolDictionaries: '' category: 'Kernel-Chronology'! + Timespan class + instanceVariableNames: 'defaultOffset'! !Timespan commentStamp: 'dtl 7/11/2009 16:35' prior: 0! I represent a duration starting on a specific DateAndTime.! + Timespan class + instanceVariableNames: 'defaultOffset'! Item was changed: ----- Method: Timespan class>>current (in category 'squeak protocol') ----- current + ^ self starting: (DateAndTime nowWithOffset: self defaultOffset)! - - - ^ self starting: DateAndTime now! Item was added: + ----- Method: Timespan class>>defaultOffset (in category 'configuring') ----- + defaultOffset + ^ defaultOffset! Item was added: + ----- Method: Timespan class>>globalize (in category 'configuring') ----- + globalize + "By default, Timespans will be created with a local timezone's offset." + defaultOffset := Duration zero! Item was added: + ----- Method: Timespan class>>initialize (in category 'initialize-release') ----- + initialize + self globalize! Item was added: + ----- Method: Timespan class>>localize (in category 'configuring') ----- + localize + "By default, Timespans will be created with a local timezone's offset." + defaultOffset := DateAndTime localOffset! Item was changed: ----- Method: Timespan class>>new (in category 'squeak protocol') ----- new "Answer a Timespan starting on the Squeak epoch: 1 January 1901" + ^ self starting: (DateAndTime new offset: self defaultOffset)! - - ^ self starting: DateAndTime new - ! Item was changed: ----- Method: Year class>>year: (in category 'squeak protocol') ----- + year: aYear + ^ self starting: + (DateAndTime + year: aYear + month: 1 + day: 1 + hour: 0 + minute: 0 + second: 0 + offset: self defaultOffset)! - year: aYear - - ^ self starting: (DateAndTime year: aYear month: 1 day: 1).!

1 0

Jump to page: