[pmwiki-users] {(...)} markup recipe available

Kathryn Andersen kat_lists at katspace.homelinux.org
Thu Apr 12 17:35:22 CDT 2007


On Thu, Apr 12, 2007 at 05:09:26PM -0500, Patrick R. Michaud wrote:
> On Thu, Apr 12, 2007 at 05:47:21PM -0400, The Editor wrote:
> > BTW, it may be a small thing, but I really l wish you had gone with
> > time not ftime.  Is there a reason you made that choice Pm?
> 
> The biggest reason was to leave the {(time ...)} expression available
> for other purposes if we came up with any.  Some people had been
> talking about using {(time)} to return the current time as a Unix
> time value (i.e., the equivalent of {(ftime %s)} ).  

Or perhaps for timing how long something takes?
 
> There's also potential confusion that people might not recognize
> that {(time ...)} could also be used to format dates -- they
> might think it's restricted to time-of-day only.

I think this is a very good point.
 
> But I'd be perfectly happy to just make {(time ...)} the core
> standard instead of {(ftime ...)}, if people are in general
> agreement about this.

No, I think it should be ftime, for "format time".  Shorter than
"strftime", less ambiguous than "time".

Kathryn Andersen
-- 
 _--_|\     | Kathryn Andersen	<http://www.katspace.com>
/      \    | 
\_.--.*/    | GenFicCrit mailing list <http://www.katspace.com/gen_fic_crit/>
      v     | 
------------| Melbourne -> Victoria -> Australia -> Southern Hemisphere
Maranatha!  |	-> Earth -> Sol -> Milky Way Galaxy -> Universe



More information about the pmwiki-users mailing list