"Valid values are 1 through 16." Regards, Richard Schuh
> -----Original Message----- > From: CMSTSO Pipelines Discussion List > [mailto:[email protected]] On Behalf Of Paul Gilmartin > Sent: Tuesday, July 21, 2009 9:00 AM > To: [email protected] > Subject: Re: Garbage in timestamp stage output > > On Jul 21, 2009, at 09:42, Schuh, Richard wrote: > > > The help file certainly does specify it: > > > > Operands > > > > n > > specifies the number of characters to include in the > timestamp. > > Valid > > values are 1 through 16. The default is 8. If n is less than > > 16, the > > > I don't see where it's specified, either in the help file > itself, or in the excerpt you provided. It would be nice if > invalid values caused an error to be reported. (But I'm > unable to reproduce the OP's (mis-)behavior. Perhaps I'm at > a different level.) > > >> -----Original Message----- > >> [mailto:[email protected]] On Behalf Of Bruce Hayden > >> Sent: Tuesday, July 21, 2009 5:53 AM > >> > >> The discussion about timestamps had me look at the > timestamp stage, > >> and I noticed that arguments above 16 to that stage make > it produce > >> unexpected output: > >> pipe literal|timestamp 17|cons > >> 8888888888888888. > >> Ready; > >> pipe literal|timestamp 18|cons > >> È8È8È8È8È8È8È8È8.. > >> Ready; > >> > >> The help file doesn't document that the argument must be > 16 or less, > >> but then again it also doesn't specify what it does with arguments > >> larger than 16. This was tested on sublevel 20. > > -- gil >
