From 7f1e1860f26f14bc06c503a576d6511d933d3799 Mon Sep 17 00:00:00 2001 From: Mark McGranaghan Date: Thu, 1 Nov 2012 22:59:53 -0700 Subject: [PATCH] use named formats --- .../time-formatting-parsing.go | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/examples/time-formatting-parsing/time-formatting-parsing.go b/examples/time-formatting-parsing/time-formatting-parsing.go index 589753e..027f03a 100644 --- a/examples/time-formatting-parsing/time-formatting-parsing.go +++ b/examples/time-formatting-parsing/time-formatting-parsing.go @@ -34,19 +34,18 @@ func main() { // Time parsing uses the same example-based approach // as `Format`ing. These examples parse times rendered // with some of the layouts used above. + withNanos := "2006-01-02T15:04:05.999999999-07:00" t1, e := time.Parse( - "2006-01-02T15:04:05.999999999-07:00", - "2012-11-01T22:08:41.117442+00:00") + withNanos, + "2012-11-01T22:08:41.117442+00:00") p(t1) - t2, e := time.Parse( - "4:05PM", - "8:41PM") + hoursMinutes := "4:05PM" + t2, e := time.Parse(hoursMinutes, "8:41PM") p(t2) // `Parse` will return an error on malformed input // explaining the parsing problem. - _, e = time.Parse( - "Mon Jan _2 15:04:05 2006", - "8:41PM") + ansic := "Mon Jan _2 15:04:05 2006" + _, e = time.Parse(ansic, "8:41PM") p(e) }