Thank you everyone for your thoughts on this.
I dont think we want to introduce a $COMPILER$ section within the
documentation files.
You're right. If we offer support for a given compiler,
all language features should work with it exactly like
with other compilers. This is true for both core Harbour
and any reasonable libs (like our contribs). In case of
a rare exception, this information can be added in some
existing textual section. A separate section dealing with
this is for sure overkill.
[ It's also however that a compiler isn't supported *at all*
for a contrib/lib. Such information can be included in per
contrib doc intro section. ]
I can rename the $PLATFORM$ section to $ARCHITECTURE$, unless there
is a more suitable choice.
For now I'll stick with $PLATFORM$; I'm programming a list of
accepted values, though I'm also leaning toward have the list of
these dynamically built from the config folder.
$PLATFORM$ is fine here.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
