Recent change of apinames_vms.bash

[suzuki toshiya]

Dear Jansen,

Please let me ask a few small questions about apinames_vms.bash.
I never accessed with VMS, so please allow me ask some stupid
questions.

1) Bash on VMS cannot invoke the DCL commands?

File renaming is very basic task of the operating systems
with a file system. It seems that VMS has a DCL command
to do that, "RENAME". If "RENAME" is usable from Bash script,
it would be more portable than using /gnu/bin/mv. Is it
impossible?

2) Why freetype_vms0.opt is needed?

Current apinames_vms.sh generates freetype_vms0.opt,
and rename it to freetype_vms.opt immediately, regardless
with the status returned by apinames.
Writing directly to freetype_vms.opt is bad idea?

3) The "-o" option of apinames is not helpful?

The default output of "apinames" is the standard output,
but apinames has the "-o" option to specify the output filename,
since its first appearance on 2005. Is there any special
reason to let apinames write to the standard output,
and let the shell redirect it to freetype_vms0.opt?

4) VMS users do cross building for VMS running on different CPU?

This question is quite different from 3 questions in above :-)

VMS has migrated among several architectures, from VAX to Alpha,
then from Alpha to Itanium, and from Itanium to x86-64. For VMS
users, the cross building for VMS on different architectures are
popular usecase? If it is popular, the cross compilers are
separated for each target architecture, like conventional
GNU toolchains (e.g. vax-netbsdelf-gcc alpha-netbsdelf-gcc, etc)?
I'm unfamiliar with the convention of LLVM-based SDK.

Regards,
mpsuzuki