Perl 6 Summary for 2005-08-15 through 2005-08-22
All~
Welcome to another monday summary, which hopefully provides some
evidence that mondays can get better. It always feels like writing
summaries is an uphill battle, perhaps I should switch to writing about
Perl 6 Language firs
On Monday 22 August 2005 04:25 pm, Larry Wall wrote:
> On Tue, Aug 23, 2005 at 04:09:29AM +0800, Yiyi Hu wrote:
> [stuff]
> : Even if making scalar lazy might cause problem sometimes, Is it
> : possible to add a property which is like
> : my $var is lazy; to handle these situation?
>
> In Perl 6 yo
On Tue, Aug 23, 2005 at 04:09:29AM +0800, Yiyi Hu wrote:
: my( $s, $t ); $s = "value t is $t"; $t = "xyz"; print $s;
: in perl 5, it will give a warning, and won't do "right" thing.
: we have to use other way or eval '$s' before print to get a "correct" answer.
:
: So I wonder, If we can make $sca
On 8/22/05, Yiyi Hu <[EMAIL PROTECTED]> wrote:
> my( $s, $t ); $s = "value t is $t"; $t = "xyz"; print $s;
I have an answer for you that is much more detailed than what you want
to hear. The short answer is "yes".
This is possible to implement, provided you appropriately declare $t.
It all depe
Hi,
Yiyi Hu wrote:
> my( $s, $t ); $s = "value t is $t"; $t = "xyz"; print $s;
> in perl 5, it will give a warning, and won't do "right" thing.
> we have to use other way or eval '$s' before print to get a "correct"
> answer.
>
> So I wonder, If we can make $scalar lazy also. As array now is lazy
On Mon, Aug 22, 2005 at 10:51:53PM +0200, Ingo Blechschmidt wrote:
: If we go with these changes, this functionality (starting place for a
: search) would be available by using
:
: Foo::Bar<$symbol_to_lookup>; # right?
Presumably, though Foo::Bar differs from OUTER in that, for packages,
th
On Mon, Aug 22, 2005 at 20:35:40 +, Ingo Blechschmidt wrote:
> Hi,
>
> on #perl6, we were wondering how to use() modules from foreign
> languages which have an incompatible identifier syntax. E.g.:
>
> use perl5:Foo::Bar; # fine, no problem
>
> # Load JavaScript modules fr
Hi,
Larry Wall wrote:
> On Sat, Aug 20, 2005 at 10:33:03PM +, Ingo Blechschmidt wrote:
> : S02 says:
> : our $a; say $::("a"); # works
> :
> : my $a; say $::("a"); # dies, you should use:
> : my $a; say $::("MY::a"); # works
>
> That looks like somebody's relic of Perl
Hi,
on #perl6, we were wondering how to use() modules from foreign
languages which have an incompatible identifier syntax. E.g.:
use perl5:Foo::Bar; # fine, no problem
# Load JavaScript modules from JSAN
use jsan:Test.Simple; # should we simply accept the dot, or...
my( $s, $t ); $s = "value t is $t"; $t = "xyz"; print $s;
in perl 5, it will give a warning, and won't do "right" thing.
we have to use other way or eval '$s' before print to get a "correct" answer.
So I wonder, If we can make $scalar lazy also. As array now is lazy by default.
Even if making sca
On Mon, Aug 22, 2005 at 09:54:36 -0700, Larry Wall wrote:
> That's not a problem as long as you keep your positionals together.
Oh, I assumed the it's
/(* *)|(* *)/,
not
/* * */
> : If there is some really odd code signature which takes in a mess, I
> : may want to intermix pos
On Mon, Aug 22, 2005 at 10:51:25AM -0600, Eric wrote:
: Just my two cents then back to lurking. The idea of having named parameters
: with different names than the variables ++. Otherwise your public API is
: dependent on private variables which is a Bad Thing and the only thing that
: realy bug
On Fri, Aug 19, 2005 at 06:42:04PM +0300, Yuval Kogman wrote:
: On Fri, Aug 19, 2005 at 08:27:38 -0700, Larry Wall wrote:
:
: > Plus I still think it's a really bad idea to allow intermixing of
: > positionals and named. We could allow named at the beginning or end
: > but still keep a constraint
Just my two cents then back to lurking. The idea of having named parameters
with different names than the variables ++. Otherwise your public API is
dependent on private variables which is a Bad Thing and the only thing that
realy bugged me about current named parameters in P6.
BTW why is it th
On 8/22/05, Larry Wall <[EMAIL PROTECTED]> wrote:
> I think the simplest thing is to say that you can't bind to the name
> of the slurpy hash. You give a name to it so that you can refer to it
> inside, but that name is not visible to binding.
Fixed in https://svn.perl.org/perl6/doc. Thanks.
Lu
On Mon, Aug 22, 2005 at 06:05:06PM +0800, Yiyi Hu wrote:
: svnbot6 r6401 | iblech++ | *%slurpy_hashes exist :)
: svnbot6 r6401 | iblech++ | It uses the semantics of
: svnbot6 r6401 | iblech++ |
: http://www.nntp.perl.org/group/perl.perl6.language/22860, i.e.
: svnbot6 r6401 | iblech++ | s
svnbot6 r6401 | iblech++ | *%slurpy_hashes exist :)
svnbot6 r6401 | iblech++ | It uses the semantics of
svnbot6 r6401 | iblech++ |
http://www.nntp.perl.org/group/perl.perl6.language/22860, i.e.
svnbot6 r6401 | iblech++ | sub foo (*%hash) {...}, foo(hash =>
{...}); # works
svnbot6
17 matches
Mail list logo
