Hi Pritpal,
> $SEEALSO$
> comma separated list of references
> $END$
> */
>
> And it does not include the $TEMPLATE$.
> Later in one example it is present:
You're right should, though I didn't have time
to review the whole document, I got lost when
trying to find out what values are accepted,
and I saw an avalanche of things to properly
define. As a start we should just add $TEMPLATE$
there, but to be honest I don't know its purpose,
and why it was added.
> 2. $COMPLIANCE$
> IsLeapYr() works exactly like CA-Cl*pper's IsLeapYr(), if your
> CA-Cl*pper doesn't have such a function you're probably in a
> different universe from the author of this function.
>
> My understanding suggests that instead of "description" it
> should be "data", like Clipper 5.3, Xbase++, ...
> a comma separated list of compilers and/or OS's.
Yes, it should. Finally for core SVN, it can only
have the value "CA-Cl*pper 5.2e", or "CA-Cl*pper 5.3b".
Well, in some rare occasions "Six", or maybe some
other products for OOP keyword.
For non-core parts, it may have any value, which the
given package is designed to comply with. ("Xbase++",
"Xbase++ Parts (XBP)", "Telepath(y)", etc.)
> 3. $NAME$
>
> Should it contain opening/closing braces "()".
Yes. To functions differentiate from commands.
> I think it should be the part of $SYNTAX$.
$NAME$ is just the keyword described in the
given doc, without any syntax fluffs, include
header and whatnot.
F.e.
SET DATE
vs.
SET DATE FORMAT [TO] <cDateFormat>
SET DATE [TO] AMERICAN | ansi | british | french
| german | italian | japan | usa
Brgds,
Viktor
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
