On 2009 Feb 22, at 22:47, pugs-comm...@feather.perl6.nl wrote:
+    $?PUGS_VERSION # Pugs version (not canonical)
+ $*PUGS_HAS_HSPLUGINS # True if Pugs was compiled with support for hsplugins
+                         # (not canonical)

These should not be part of the standard. But while Pugs is free to keep providing them, I would suggest the more general:

> $?PERL6_IMPLEMENTATION (pugs, rakudo, ...)
> $?PERL6_IMPL_VERSION
> $?PERL6_IMPL_FEATURES (it's possible this should be part of %?CONFIG)

(BTW, why is a "this impl compiled with support for" not a ? twigil? It's not going to change at runtime.)

+There were threads on p6l about unifying all variables which concern the OS or +the VM ($*UID, $*PROGRAM_NAME, etc.) into two variables, $?ENV (compile-time +environment) and $*ENV (runtime environment). Larry did like the idea, but

%?PERL6_ENV
%*PERL6_ENV

BTW, I also agree with the earlier observation that $*OUT vs. $*DEFOUT (etc.) both violates Huffman coding and encourages use of the wrong one. $*OUT vs. $*STDOUT (meanings inverted relative to the above) maybe?

--
brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allb...@kf8nh.com
system administrator [openafs,heimdal,too many hats] allb...@ece.cmu.edu
electrical and computer engineering, carnegie mellon university    KF8NH


Attachment: PGP.sig
Description: This is a digitally signed message part

Reply via email to