Re: QWCCVTDT API and *DTS format

Hi Carsten,

What is a *DTS timestamp as opposed to the kind of timestamp that MOVE will
convert?

Btw, I wrote a general purpose file display program 10 years ago similar to
WRKDBF and DBU using those numeric edit API's, which is why I brought that
one up -- a really good example of how bif's are so much easier than API's,
when they're available.

Still curious,
Peter Dow
Dow Software Services, Inc.
909 425-0194 voice
909 425-0196 fax

From: "Carsten Flensburg" <flensburg@novasol.dk>
> I mostly use QWCCVTDT to convert *DTS timestamps these days - as you say,
> MOVE will do nicely for most other data conversions.
>
> In general, I prefer to use bifs if they offer the functionality I need.
> Calling an API to do something the programming language already offers in
my
> opinion only adds unnecessary complexity to a program.  - Let the compiler
> do the work - and the RPG/IV reference the documentation.
>
> Talking about the edit APIs compared to their bif counterparts you'll have
> to do two calls involving some rather exciting parameter definitions to
edit
> a numeric field, in stead of a single and simple bif expression. If you
> however require the ability to edit a field whose attributes are not known
> at compile time, the _LBEDIT (Late bound edit) builtin makes this possible
> whereas the bifs and APIs do not.



_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com