Pharo Issue Tracker - FogBugz (Case [Issue]12111) Chronology - (Date readFrom: '4.2.2013' readStream pattern: 'd.m.yy') ==>> 4 February 2020

FogBugz Notification

	Camille Teruel resolved Case 12111: (Date readFrom: '4.2.2013' readStream pattern: 'd.m.yy') ==>> 4 February 2020 and assigned it to Sabine Knöfel: Bug in Chronology: 1. Pharo Image • You are subscribed to this case

We did a pass on the date parser so that it raises errors when the input doesn't match the pattern. We also found extra bugs and created a separated TestCase for the DateParser. Now the patterns follow the spec of the DateParser class comment, that is:

" Read a Date from the stream based on the pattern which can include the tokens:

y = A year with 1 to n digits (after 2000)
yy = A year with 2 digits (after 2000)
yyyy = A year with 4 digits
m = A month with 1 or 2 digits
mm = A month with 2 digits
d = A day with 1 or 2 digits
dd = A day with 2 digits

...and any other Strings inbetween. Representing $y, $m and $d is done using
\y, \m and \d and slash itself with \\. Simple example patterns:

'yyyy-mm-dd'
'yyyymmdd'
'yy.mm.dd'
'y-m-d'
"

Pablo and Camille

Status changed:
Work Needed (Conclusion)

Resolved (Fix Review Needed)

Assigned To changed:
Everyone

Sabine Knöfel

	Priority: 5 – Fix If Time		Status: Resolved (Fix Review Needed)
	Assigned to: Sabine Knöfel		Milestone: Pharo3.0

Go to Case

No longer need updates? Unsubscribe from this case.

Don't want FogBugz notifications anymore? Update your preferences.

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker