On Tue, Aug 14, 2001 at 09:55:37AM -0500, Garrett Goebel wrote:
> > There should be ONE calling style for each sub/method.
> > Allowing this _will_ cause different people to use different
> > calling styles and also possible confusion.
>
> It gives us a cleaner way to mix and match order dependa
From: Michael G Schwern [mailto:[EMAIL PROTECTED]]
> On Tue, Aug 14, 2001 at 09:55:37AM -0500, Garrett Goebel wrote:
> > > There should be ONE calling style for each sub/method.
> > > Allowing this _will_ cause different people to use different
> > > calling styles and also possible confusion.
>
Michael G Schwern wrote:
>
> I think you misunderstand. This isn't named parameters vs prototyped
> parameters vs args as list. The problem is the idea that functions
> should accept *multiple styles by default* which the proposed
> Module::Interface does.
No, it doesn't. Unfortunately, I used
On Tue, 14 Aug 2001, Nathan Wiger wrote:
> This is very similar to what Params::Validate does right now; in fact,
> the module could well inherit from it.
That'd be tricky since its not OO but you could build on it.
Alternately, I'd be happy to add more features to Params::Validate (I
don't feel
Graham Barr <[EMAIL PROTECTED]> writes:
> > > (1) Foo vs Foo_XS
>
> Why do they need to be named differently ? Only one will be installed.
That is only possible if they have _identical_ APIs.
-- Johan
On Mon, Aug 13, 2001 at 10:45:27AM +0100, Graham Barr wrote:
> On Sat, Aug 11, 2001 at 07:20:11PM -0400, [EMAIL PROTECTED] wrote:
> > On Sat, Aug 11, 2001 at 02:16:49PM -0500, Jarkko Hietaniemi wrote:
> > > One silliness is that the implementation "style" of the module
> > > seems to creep to the
On Mon, Aug 13, 2001 at 10:02:29AM -0500, Jarkko Hietaniemi wrote:
> On Mon, Aug 13, 2001 at 09:46:13AM -0500, Garrett Goebel wrote:
> > From: Jarkko Hietaniemi [mailto:[EMAIL PROTECTED]]
> > >
> > > Remember, the goal for Perl 6 is to allow several modules sharing
> > > the same name.
> >
> > D
From: Graham Barr [mailto:[EMAIL PROTECTED]]
> On Mon, Aug 13, 2001 at 04:38:43PM -0700, Nathan Wiger wrote:
> > And allow flexible calling styles. For example, you might say:
> >
> ># import args() for argument validation
> >use Module::Interface qw/args/;
> >
> >sub my_func (@) {
>
Hello all.
There's been a load of discussion about the implementation of Perl 6 in
various places recently: at TPC, on language-dev, on python-dev, and in
various emails shot back and forth between some of the participants.
Conspicuously missing in that list of places is perl6-internals, wher
(I figured it'd take me longer to track this information down myself than it
would to get a response from the list. Laziness... :)
Can properties be temp()orarily masked? For example:
foreach my $array (@arrays)
{
temp $array.sep = ', '; # assuming this is a real property
p
Any word from on high whether subroutine signatures will apply to methods in
Perl6? There's RFC128 and RFC97... but they both mostly dodge the issue of
methods.
The absense of method signatures for specifying required, optional, and
named parameters... not to mention type-checking for validation
Three variable scope declarators, three different behaviors (as recent as
5.7.2)
(Set One)
$a = 'a';
{
my $a .= 'b', $a .= 'c' if $a .= 'd', $a .= 'e';
}
print $a, "\n"; # adec
$b = 'a';
{
local $b .= 'b', $b .= 'c' if $b .= 'd', $b .= 'e';
}
print $b, "\n";# ade
$
12 matches
Mail list logo
