- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] inconsistent FileReference

by Esteban Lorenzano

it is not inconsistent, last option is incorrect and should not be used. what you do there is to declare: directory âtmp', file âa/b/c.txtâ is casual that it coincides with a real path, but it is not semantically correct, thatâs why x ~= z there was an issue around to explicitly forbid to declare a file like that, but I was (and still am) not sure it should be forbiddenâ¦ is not the spirit of smalltalkâ¦ you know, great power/great responsibility thing :) but it causes confusions (as this one), so at least needs to be correctly explained somewhere :) cheers, Esteban > On 09 Jul 2016, at 13:11, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Imagine that you have > > '/tmp/a/b' folder containing 'c' file > > '/tmp/a/b' asFileReference ensureCreateDirectory. > '/tmp/a/b/c' asFileReference writeStreamDo: [ :s | s nextPutAll: 'contents' ]. > > now there are three ways how you can see the contents of the c file > > x := '/tmp/a/b/c.txt' asFileReference. > y := '/tmp' asFileReference / 'a' / 'b' / 'c.txt'. > z := '/tmp' asFileReference / 'a/b/c.txt'. > > They clearly all point to the same file: > > x contents = y contents "true" > x contents = z contents "true" > > Yet the last option is different > > x = y "true" > x = z "false" > > Why is that? Because the parent is different: > > x parent pathString "'/tmp/a/b'" > y parent pathString "'/tmp/a/b'" > z parent pathString "'/tmp'" > > So the parent is based on how the reference was constructed, not what it is actually pointing to, which is stupid. > > Is this a bug? Is this a (nasty) expected behavior? > > Peter

July 9, 2016

inconsistent FileReference

by Peter UhnÃ¡k

Imagine that you have '/tmp/a/b' folder containing 'c' file '/tmp/a/b' asFileReference ensureCreateDirectory. '/tmp/a/b/c' asFileReference writeStreamDo: [ :s | s nextPutAll: 'contents' ]. now there are three ways how you can see the contents of the c file x := '/tmp/a/b/c.txt' asFileReference. y := '/tmp' asFileReference / 'a' / 'b' / 'c.txt'. z := '/tmp' asFileReference / 'a/b/c.txt'. They clearly all point to the same file: x contents = y contents "true" x contents = z contents "true" Yet the last option is different x = y "true" x = z "false" Why is that? Because the parent is different: x parent pathString "'/tmp/a/b'" y parent pathString "'/tmp/a/b'" z parent pathString "'/tmp'" So the parent is based on how the reference was constructed, not what it is actually pointing to, which is stupid. Is this a bug? Is this a (nasty) expected behavior? Peter

July 9, 2016

Re: [Pharo-dev] [squeak-dev] Time now print24

by stepharo

I like the idea of Go to have a separate date-printer. Stef Le 8/7/16 Ã 11:23, Sven Van Caekenberghe a Ã©crit : >> On 08 Jul 2016, at 10:49, Tobias Pape <Das.Linux(a)gmx.de> wrote: >> >> >> On 07.07.2016, at 18:33, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> >>> Hi All, >>> >>> how does one produce a nice timestamp, simply date and time as in >>> >>> 7/7/2016 09:19:38 >> What's with 'TimeStamp now' (prints '8 July 2016 10:34:36 am') >> >> or this one: >> >> TimeStamp now in: [:t | >> String streamContents: [:s | >> t asDate printOn: s format: #(2 1 3 $/ 1 1 2). >> s space. >> t asTime print24: true showSeconds: true on: s]] >> >> Too bad TimeStamp is deprecated in Pharo4, so this works in pharo: > Yes, it is gone. It was a subclass whose only feature was a different print representation. It was also confusing, why choose it or DateAndTime. > > We folded TimeStamp's functionality into DateAndTime (see #printSeparateDateAndTimeOn: and #readSeparateDateAndTimeFrom:) > >> DateAndTime now rounded in: [:t | >> String streamContents: [:s | >> t asDate printOn: s format: #(2 1 3 $/ 1 1 2). >> s space. >> t asTime print24: true showSeconds: true on: s]] >> >> But DateAndTime knows no #rounded in Squeak, buuut: >> >>> ======================= >> This works for both: >> >> >> DateAndTime now in: [:t | >> String streamContents: [:s | >> t asDate printOn: s format: #(2 1 3 $/ 1 1 2). >> s space. >> t printHMSOn: s]] >> >> ===== >> >> Best regards >> -Tobias >> >> PS: I'd prefer ISO, nonetheless: https://xkcd.com/1179/ > Yes, that was my point exactly. Thanks for the cool link! > > In the same line, the AM/PM don't make sense, and the timezone (or Z) is required. > > https://en.wikipedia.org/wiki/ISO_8601 > > Something like 2016-07-08 08:41:52 Z or 2016-07-08 08:41:52 +00:00 is perfectly readable. > > BTW, these are unambigiously parseable as well (for example, using ZTimestamp). > > ZTimestamp readFromString: '2016-07-08 08:41:52 Z'. > > "2016-07-08T08:41:52Z" > > ZTimestamp readFromString: '2016-07-08 08:41:52 +00:00'. > > "2016-07-08T08:41:52Z" > > Using ZTimestampFormat, which is an example based formatter/parser, like Go's, you can easily produce this slightly more human friendly format. > > (ZTimestampFormat fromString: '2001-02-03 16:05:06 +00:00') format: DateAndTime now. > > "'2016-07-08 11:16:54 +02:00'" > > And the reverse (obviously you share/predefine/cache the specific format object). > > (ZTimestampFormat fromString: '2001-02-03 16:05:06 +00:00') createDateAndTime; parse: '2016-07-08 11:16:54 +02:00'. > > "2016-07-08T11:16:54+02:00" > >> (or the German way: 25.12.2015 :P) >> >> >> >>> Trivial, right? >>> >>> So >>> >>> Date today mmddyyyy, ' ', Time now print24 '7/7/2016 09:22:40.914' >>> >>> .914, ah, nanos. How useful. Let's get rid of them. No nanos: accessor so >>> >>> Date today mmddyyyy, ' ', (Time now nanos: 0) print24 => MNU >>> >>> but there's a seconds accessor, so >>> >>> Date today mmddyyyy, ' ', (Time now seconds: Time now seconds; print24) '7/7/2016 00:00:41 >>> >>> ?? So seconds: is private, and isn't the dual of Time seconds: >>> >>> Time seconds >>> ^ self second >>> Time second >>> ^ self asDuration seconds >>> Duration seconds >>> "Answer the number of seconds the receiver represents." >>> ^seconds rem: SecondsInMinute >>> >>> Looks broken to me. >>> >>> Personally I think print24 should not print sub seconds. >>> >>> cc'ing to Pharo because I want this timestamp to be the same in both dialects for a profiling tool we want to use in both dialects. >>> _,,,^..^,,,_ >>> best, Eliot >> >> > >

July 9, 2016

Re: [Pharo-dev] Spec Tutorial First chapter

by Sven Van Caekenberghe

> On 08 Jul 2016, at 19:50, stepharo <stepharo(a)free.fr> wrote: > > Hi > > Johan Fabry is writing a great tutorial (and this is cool to see all the material I gathered or wrote with him in the past) > > to take such great form. > > I attached the first chapter. I will post the chapter one by one once I review them (so far I have nothing to do - great feeling). > > Well done Johan! > > Stef > > <FirstContact.pdf> Great work, thank you ! Books make a lot of difference, even today.

July 9, 2016

Re: [Pharo-dev] AthensCairoSurface not getting garbage collected

by Igor Stasenko

If problem in ever-growing cache - try using identical object(s) as keys for cache, not newly-created-unique one, each time you adding new entry to cache :) or.. maybe cache is broken and does not releasing garbage anymore. On 8 July 2016 at 16:54, J.F. Rick <self(a)je77.com> wrote: > I don't have enough evidence either way, but the signs point to no since > the applications that crash are not ones that use form-based paints. I > assume they wouldn't be affected by the flush. We did have one crash on a > form-based one where it crashed after running for 10 hours. My guess is > that one ran out of memory. That crash is probably resolved. But, I'll keep > everybody informed as I work more on it. > > Cheers, > > Jeff > > > On Thu, Jul 7, 2016 at 3:28 AM Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > >> Jeff, does this flush reduces the amount of crash you are experiencing? >> >> Alexandre >> >> > On Jul 6, 2016, at 9:01 PM, J.F. Rick <self(a)je77.com> wrote: >> > >> > Nicolai, >> > >> > THANKS! That worked. I no longer have any AthensCairoCanvas hanging >> around after executing "CairoBackendCache flush". >> > >> > Cheers, >> > >> > Jeff >> > >> > On Sun, Jul 3, 2016 at 11:58 AM Nicolai Hess <nicolaihess(a)gmail.com> >> wrote: >> > Hi Jeff, >> > >> > if you use forms to paint on an AthensCairoCanvas, they are cached in >> the CairoBackendCache, >> > can you try to flush that cache whith >> > CairoBackendCache flush. >> > >> > >> > 2016-06-18 18:36 GMT+02:00 J.F. Rick <self(a)je77.com>: >> > I'm using Athens rendering for my multi-touch applications on Pharo5. >> As part of that, I create a surface: >> > surface := AthensCairoSurface extent: bounds extent asIntegerPoint. >> > >> > Though the object creating that surface is deleted, the surface sticks >> around. So, each time I run the app, I get another instance of >> AthensCairoSurface hanging around. That means all the forms stick around as >> well. So my image can quickly grow towards the 1GB size. >> > >> > Is there anything I can do about that? Can I manually get the surface >> to delete itself? >> > >> > Cheers, >> > >> > Jeff >> > >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> -- Best regards, Igor Stasenko.

July 9, 2016

Re: [Pharo-dev] [squeak-dev] Re: Time now print24

by David T. Lewis

On Fri, Jul 08, 2016 at 09:11:46PM -0500, Chris Muller wrote: > Eliot, I'm not against your suggestion about seconds:, but there is no > way you should have to mutate an object for sake of only printing it. > It should merely be the responsibility of the printing to meet the > needed requirement. +1 Dave > > On Fri, Jul 8, 2016 at 12:49 AM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi All, > > > > On Jul 7, 2016, at 9:33 AM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > Hi All, > > > > how does one produce a nice timestamp, simply date and time as in > > > > 7/7/2016 09:19:38 > > > > Trivial, right? > > > > So > > > > Date today mmddyyyy, ' ', Time now print24 '7/7/2016 09:22:40.914' > > > > .914, ah, nanos. How useful. Let's get rid of them. No nanos: accessor so > > > > Date today mmddyyyy, ' ', (Time now nanos: 0) print24 => MNU > > > > but there's a seconds accessor, so > > > > Date today mmddyyyy, ' ', (Time now seconds: Time now seconds; print24) > > '7/7/2016 00:00:41 > > > > ?? So seconds: is private, and isn't the dual of Time seconds: > > > > Time seconds > > ^ self second > > Time second > > ^ self asDuration seconds > > Duration seconds > > "Answer the number of seconds the receiver represents." > > ^seconds rem: SecondsInMinute > > > > Looks broken to me. > > > > > > Let me be more explicit, and ask for permission to fix this. One basic bug > > is the asymmetry between seconds, an accessor that answers seconds mod 60, > > and seconds: that doesn't set seconds mod 60. But seconds: is private and > > could be replaced by eg setTotalSeconds:, presumably without breaking > > clients, allowing seconds: to be redefined to do the right thing. > > > > I note that the historic bug of changing the semantics of Time now to answer > > something with finer resolution than one second could have been avoided by > > adding eg exactlyNow or preciselyNow. > > > > The problem with nanos (apart from the horrible abbreviation) is that it > > presumes a maximum precision that isn't well chosen. Microseconds work out > > much better. And I hope we change the internal representation accordingly. > > But there needs to be done accessor that rounds to the nearest second > > without revealing the internal precision. Time now toTheNearestSecond or > > Time theNearestSecondNow or...? > > > > > > Personally I think print24 should not print sub seconds. > > > > cc'ing to Pharo because I want this timestamp to be the same in both > > dialects for a profiling tool we want to use in both dialects. > > _,,,^..^,,,_ > > best, Eliot > > > > > > > >

July 9, 2016

Re: [Pharo-dev] [squeak-dev] Re: Time now print24

by David T. Lewis

On Thu, Jul 07, 2016 at 10:49:10PM -0700, Eliot Miranda wrote: > Hi All, > > > On Jul 7, 2016, at 9:33 AM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > Hi All, > > > > how does one produce a nice timestamp, simply date and time as in > > > > 7/7/2016 09:19:38 > > > > Trivial, right? > > > > So > > > > Date today mmddyyyy, ' ', Time now print24 '7/7/2016 09:22:40.914' > > > > .914, ah, nanos. How useful. Let's get rid of them. No nanos: accessor so > > > > Date today mmddyyyy, ' ', (Time now nanos: 0) print24 => MNU > > > > but there's a seconds accessor, so > > > > Date today mmddyyyy, ' ', (Time now seconds: Time now seconds; print24) '7/7/2016 00:00:41 > > > > ?? So seconds: is private, and isn't the dual of Time seconds: > > > > Time seconds > > ^ self second > > Time second > > ^ self asDuration seconds > > Duration seconds > > "Answer the number of seconds the receiver represents." > > ^seconds rem: SecondsInMinute > > > > Looks broken to me. > > Let me be more explicit, and ask for permission to fix this. One basic bug is the asymmetry between seconds, an accessor that answers seconds mod 60, and seconds: that doesn't set seconds mod 60. But seconds: is private and could be replaced by eg setTotalSeconds:, presumably without breaking clients, allowing seconds: to be redefined to do the right thing. > Yes please fix it. It is clearly wrong to have #seconds and #seconds: refer to two different things. And since #seconds: is private, that would be the thing to change. Changing it to #setTotalSeconds: would be good, although I note that there is a #asSeconds method too, so maybe #setSeconds: might match better with #asSeconds. But either would be fine, and yes please, go ahead and fix it. > I note that the historic bug of changing the semantics of Time now to answer something with finer resolution than one second could have been avoided by adding eg exactlyNow or preciselyNow. > I'm not sure it is a bug, more like a difference in presentation versus internal representation. I think that #now should mean "now", not "now rounded to the nearest second". But if I display the time now, I probably would prefer it to be displayed to the nearest second. > The problem with nanos (apart from the horrible abbreviation) is that it presumes a maximum precision that isn't well chosen. Microseconds work out much better. And I hope we change the internal representation accordingly. But there needs to be done accessor that rounds to the nearest second without revealing the internal precision. Time now toTheNearestSecond or Time theNearestSecondNow or...? > Absolutely right. In the UTCDateAndTime changes, the magnitude of DateAndTime is utcMicroseconds for exactly this reason. That does not preclude nanosecond precision, it just means that the common case of microsecond precision uses an integer, and higher precisions are represented as Fraction. So the common case is fast, and higher precision remains possible. Somewhat more generally, the scale is in units of seconds. Precision should be unlimited (any Number) and accuracy is dependent on the underlying system clock (milliseconds or maybe microseconds if you are lucky). Most everyday computers may be accurate to milliseconds but report precision to microseconds. Specialized real time systems (e.g. GPS) may legitimately deal with higher accuracies and are probably not lying if they claim nanosecond precision. Human beings may drift a few hours one way or the other without noticing the difference, and are thus generally satisfied with full second precision and not much accuracy at all ;-) Dave > > > > Personally I think print24 should not print sub seconds. > > > > cc'ing to Pharo because I want this timestamp to be the same in both dialects for a profiling tool we want to use in both dialects. > > _,,,^..^,,,_ > > best, Eliot >

July 9, 2016

Re: [Pharo-dev] [squeak-dev] Re: Time now print24

by Chris Muller

> But there needs to be done accessor that rounds to the nearest second > without revealing the internal precision. Time now toTheNearestSecond or > Time theNearestSecondNow or...? Time now truncatedTo: 1 second. Time now roundedTo: 1 second.

July 9, 2016

Re: [Pharo-dev] [squeak-dev] Re: Time now print24

by Chris Muller

Eliot, I'm not against your suggestion about seconds:, but there is no way you should have to mutate an object for sake of only printing it. It should merely be the responsibility of the printing to meet the needed requirement. On Fri, Jul 8, 2016 at 12:49 AM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi All, > > On Jul 7, 2016, at 9:33 AM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi All, > > how does one produce a nice timestamp, simply date and time as in > > 7/7/2016 09:19:38 > > Trivial, right? > > So > > Date today mmddyyyy, ' ', Time now print24 '7/7/2016 09:22:40.914' > > .914, ah, nanos. How useful. Let's get rid of them. No nanos: accessor so > > Date today mmddyyyy, ' ', (Time now nanos: 0) print24 => MNU > > but there's a seconds accessor, so > > Date today mmddyyyy, ' ', (Time now seconds: Time now seconds; print24) > '7/7/2016 00:00:41 > > ?? So seconds: is private, and isn't the dual of Time seconds: > > Time seconds > ^ self second > Time second > ^ self asDuration seconds > Duration seconds > "Answer the number of seconds the receiver represents." > ^seconds rem: SecondsInMinute > > Looks broken to me. > > > Let me be more explicit, and ask for permission to fix this. One basic bug > is the asymmetry between seconds, an accessor that answers seconds mod 60, > and seconds: that doesn't set seconds mod 60. But seconds: is private and > could be replaced by eg setTotalSeconds:, presumably without breaking > clients, allowing seconds: to be redefined to do the right thing. > > I note that the historic bug of changing the semantics of Time now to answer > something with finer resolution than one second could have been avoided by > adding eg exactlyNow or preciselyNow. > > The problem with nanos (apart from the horrible abbreviation) is that it > presumes a maximum precision that isn't well chosen. Microseconds work out > much better. And I hope we change the internal representation accordingly. > But there needs to be done accessor that rounds to the nearest second > without revealing the internal precision. Time now toTheNearestSecond or > Time theNearestSecondNow or...? > > > Personally I think print24 should not print sub seconds. > > cc'ing to Pharo because I want this timestamp to be the same in both > dialects for a profiling tool we want to use in both dialects. > _,,,^..^,,,_ > best, Eliot > > > >

July 9, 2016

Re: [Pharo-dev] [squeak-dev] Time now print24

by Brad Selfridge

+100 for ISO. ----- Brad Selfridge -- View this message in context: http://forum.world.st/Time-now-print24-tp4905425p4905677.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 8, 2016