From @moritz

11​:17 < moritz_> rakudo​: say now
11​:17 <+p6eval> rakudo 2c8bb8​: OUTPUT«Could not find sub &now␤ in main
program
  body at line 22​:/tmp/NfyPhq3Vve␤»
11​:17 < moritz_> I thought that worked?
11​:19 < moritz_> rakudo​: time
11​:19 <+p6eval> rakudo 2c8bb8​: OUTPUT«Could not find sub &time␤ in main
  program body at line 22​:/tmp/VN3fzPeGjd␤»

I guess it was broken by e682712b418bcd2aadfc9a9cefdeac427fade722

From @Kodiologist

On Fri Sep 17 02​:26​:49 2010, moritz wrote​:

11​:17 < moritz_> rakudo​: say now
11​:17 <+p6eval> rakudo 2c8bb8​: OUTPUT«Could not find sub &now␤ in main
program
body at line 22​:/tmp/NfyPhq3Vve␤»
11​:17 < moritz_> I thought that worked?
11​:19 < moritz_> rakudo​: time
11​:19 <+p6eval> rakudo 2c8bb8​: OUTPUT«Could not find sub &time␤ in main
program body at line 22​:/tmp/VN3fzPeGjd␤»

I guess it was broken by e682712b418bcd2aadfc9a9cefdeac427fade722

'now' and 'time' seem to work fine except in an -e string, and in an
-e string they'll still work—unless one of them is at the very end,
without any trailing whitespace or semicolons.

The RT System itself - Status changed from 'new' to 'open'

From @pmichaud

'time' and 'now' seem to work even in a -e string​:

pmichaud@​orange​:~/rakudo$ ./perl6 -e 'say time'
1296682851
pmichaud@​orange​:~/rakudo$ ./perl6 -e 'say now'
Instant​:2011-02-02T21​:40​:55.901512Z

I'm guessing this ticket can be closed if we have sufficient spectests
for 'time' and 'now'.

Pm

From @zhuomingliang

I think it can be closed. there was already some tests use time && now.
see S29-context/sleep.t and S32-temporal/DateTime.t

@moritz - Status changed from 'open' to 'resolved'