r11754: MAYBE_FLAT deprecated?
Audrey Tang
In r11754, you had deprecated the use of the MAYBE_FLAT flag, but there
is no mention of this in the commit log.
Consider this Perl 6 snippet:
foo(@x, @y);
sub foo (@x, @y) { }
versus:
foo(@x, @y);
sub foo (*@z) { }
how should I emit the call for foo() without knowing about &foo's
signature before hand, without triggering the deprecation?
Thanks,
Audrey
Chip Salzenberg
> In r11754, you had deprecated the use of the MAYBE_FLAT flag, but there
> is no mention of this in the commit log.
I just thought nobody was using it; braino. I didn't intend it to go away
until we had gone through a public discussion to catch any users who weren't
in the core tree.
Consider it undeprecated, I'll update the docs (and consider how to describe
it so it doesn't sound like something that should be deprecated).
--
Chip Salzenberg <ch...@pobox.com>
Chip Salzenberg
Pugs. What say?
6 MAYBE_FLAT
If this bit is set on a PMC value, and:
(a) the PMC is either an aggregate or a scalar containing a
reference to an aggregate, and
(b) the target register has the SLURPY bit set,
then pass the PMC value as a list of values, in these ways:
(a) if the value is an array, pass its elements in the normal
way (FLAT style);
(b) if the value is a hash, pass its elements as a list of
key/value pairs contained in HLL-specific 'pair' PMCs.
The meaning of this bit is undefined when applied to integer,
number, and string values. It may not be combined with the
NAMED bit.
Note the "HLL-specific" clause, which allows Pugs and other HLLs to differ
on what the ideal 'pair' PMC is.
--
Chip Salzenberg <ch...@pobox.com>