[svn:parrot] r45651 - trunk/config/gen/config_pm
plobsing at svn.parrot.org
plobsing at svn.parrot.org
Wed Apr 14 02:53:50 UTC 2010
Author: plobsing
Date: Wed Apr 14 02:53:49 2010
New Revision: 45651
URL: https://trac.parrot.org/parrot/changeset/45651
Log:
describe new structure of config hash
fixes TT1474
Modified:
trunk/config/gen/config_pm/config_pir.in
Modified: trunk/config/gen/config_pm/config_pir.in
==============================================================================
--- trunk/config/gen/config_pm/config_pir.in Wed Apr 14 02:40:48 2010 (r45650)
+++ trunk/config/gen/config_pm/config_pir.in Wed Apr 14 02:53:49 2010 (r45651)
@@ -12,9 +12,9 @@
# store the config data into $P0
$P0 = _config()
# Retrieve and print a key
- $P1 = $P0["cc"]
+ $S1 = $P0["cc"]
print "Your C compiler is "
- print $P1
+ print $S1
print "\n"
...
@@ -25,14 +25,14 @@
config.pir is a mechanism for accessing most of the data collected by
Configure. It's roughly equivalent to Perl5's C<Config.pm> module.
-At the end of a successful C<make> of Parrot, a PASM file generated by
+At the end of a successful C<make> of Parrot, a PIR file generated by
Configure is run to put a file, F<config.fpmc>, into the library with a
frozen Hash of the configuration data. This library provides a
function, C<_config>, to unpack and return that file's data.
C<_config> does not take any parameters. It returns a single Hash
containing the data. Keys that were C<undef> in Configure contain a
-C<None> PMC; otherwise they contain a C<String>.
+null string; otherwise they contain a non-null, possibly empty, string.
Note that the behavior of that hash when writing to any value (especially
undefined values) is undefined, and may be rather funky.
More information about the parrot-commits
mailing list