Re: [perl6/specs] 58fe2d: [S12] spec setting and getting values of attribute...

2010-09-30 Thread Brandon S Allbery KF8NH
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/1/10 00:31 , Brandon S Allbery KF8NH wrote: > As for serializeability, I think .perl is being used for two different > things and we need to separate them. If it's there for debugging, you want Addendum, since as I reread my message it looks a

Re: [perl6/specs] 58fe2d: [S12] spec setting and getting values of attribute...

2010-09-30 Thread Brandon S Allbery KF8NH
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 9/30/10 16:46 , Moritz Lenz wrote: > 1) please don't abuse MONKEY_TYPING for anything that might look like > dangerous If Perl 6 is still Perl then in some sense it implies that "dangerous" is accepted practice. :) That said... > 2) I find .perl

Re: [perl6/specs] 58fe2d: [S12] spec setting and getting values of attribute...

2010-09-30 Thread Timothy S. Nelson
On Thu, 30 Sep 2010, Damian Conway wrote: And thus C<.get_value> and C<.set_value> are just convenient access points for the same behaviour. Yes. People are going to shoot themselves in the foot anyway, so let's legalize semi-automatic weapons as well. Well, of course! What are you, a soci

Re: [perl6/specs] 58fe2d: [S12] spec setting and getting values of attribute...

2010-09-30 Thread Timothy S. Nelson
On Fri, 1 Oct 2010, Damian Conway wrote: Jonathan wrote: Sounds like the encapsulation breaking thingy probably wants to be looking for some pragma to have been used in the lexical scope of the caller, maybe. I'd rather that we called it something other than MONKEY_TYPING though. Different evi

Re: [perl6/specs] 58fe2d: [S12] spec setting and getting values of attribute...

2010-09-30 Thread Darren Duncan
Moritz Lenz wrote: Darren Duncan wrote: I think then that .perl needs to be updated so it is more expressly limited and only works on some objects rather than on all of them. The way I see it, .perl is mainly about representing *value* objects in a serialized form, and what it should produce

Re: not using get/set (was Re: [perl6/specs] 4d77c0: ...)

2010-09-30 Thread Darren Duncan
Jonathan Worthington wrote: On 30/09/2010 21:38, Darren Duncan wrote: Mark J. Reed wrote: Of alternatives you didn't mention, I like "put" - as pithy as "get" and "set", with plenty of corresponding history (SmallTalk, POSIX, HTTP,...). Actually, *yes*. I didn't think of this one at the tim

Re: [perl6/specs] 58fe2d: [S12] spec setting and getting values of attribute...

2010-09-30 Thread Damian Conway
Jonathan wrote: > Sounds like the encapsulation breaking thingy probably wants to be looking > for some pragma to have been used in the lexical scope of the caller, maybe. > I'd rather that we called it something other than MONKEY_TYPING though. > Different evil, different pragma. :-) As long as

Re: [perl6/specs] 58fe2d: [S12] spec setting and getting values of attribute...

2010-09-30 Thread Jonathan Worthington
On 30/09/2010 10:49, Damian Conway wrote: As long as C<.perl> works the way it does, there can be no real privacy. Sigh. That is indeed badly broken. Surely it ought to default to C, and require class architects to override .perl explicitly if they wish to break encapsulation. I see/use .perl

Re: [perl6/specs] 58fe2d: [S12] spec setting and getting values of attribute...

2010-09-30 Thread Damian Conway
Moritz writes: >> Objects that you can't do that with don't make sense to be serialized and so >> .perl can reasonably refuse to work on them. > > method perl { >die "Can't serialize objects of type $?CLASS, because ..."; > } Sure. But now the cautious programmer has to add that to *every* cl

Re: not using get/set (was Re: [perl6/specs] 4d77c0: ...)

2010-09-30 Thread Jonathan Worthington
On 30/09/2010 21:38, Darren Duncan wrote: Mark J. Reed wrote: Of alternatives you didn't mention, I like "put" - as pithy as "get" and "set", with plenty of corresponding history (SmallTalk, POSIX, HTTP,...). Actually, *yes*. I didn't think of this one at the time but when you mentioned the

[perl #78100] tests available

2010-09-30 Thread kyleha
This is an automatically generated mail to inform you that tests are now available in S32-str/comb.t commit c6cca58b1624f5cd5c6735c6a212c466fe3f223c Author: Moritz Lenz Date: Thu Sep 30 22:52:25 2010 +0200 unfudge tests for RT #78100, patrickas++ diff --git a/S32-str/comb.t b/S32-str/com

Re: [perl6/specs] 58fe2d: [S12] spec setting and getting values of attribute...

2010-09-30 Thread Moritz Lenz
Darren Duncan wrote: > Carl Mäsak wrote: >> To summarize, I consider myself having lost that debate. I even >> demonstrate the complete unviability of my views (that privacy has any >> kind of footing in Perl 6) with the below one-liner. >> >> rakudo: class X { has $!foo; has $!bar; has $!baz };

Re: [perl6/specs] 58fe2d: [S12] spec setting and getting values of attribute...

2010-09-30 Thread Darren Duncan
Carl Mäsak wrote: To summarize, I consider myself having lost that debate. I even demonstrate the complete unviability of my views (that privacy has any kind of footing in Perl 6) with the below one-liner. rakudo: class X { has $!foo; has $!bar; has $!baz }; say eval(X.new( foo => 1, bar => 2,

[perl #78148] [BUG] &open always opens in text mode regardless of the value of the :$bin flag in Rakudo

2010-09-30 Thread Carl Mäsak
# New Ticket Created by "Carl Mäsak" # Please include the string: [perl #78148] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=78148 > First bug report through a tweet, I think: :

Re: not using get/set (was Re: [perl6/specs] 4d77c0: ...)

2010-09-30 Thread Darren Duncan
Mark J. Reed wrote: Of alternatives you didn't mention, I like "put" - as pithy as "get" and "set", with plenty of corresponding history (SmallTalk, POSIX, HTTP,...). Actually, *yes*. I didn't think of this one at the time but when you mentioned the various history of pairs I then thought of

feather.perl6.nl temporarily down

2010-09-30 Thread Moritz Lenz
Hi, in a data center in the beautiful Netherlands, a power supply unit decided to end its existence in a cloud of smoke. Thus it's my sad duty to announce that feather.perl6.nl, the Perl 6 development server, is currently down. Two of the virtual hosts (which among other things host the perl6.org

Re: [perl6/specs] 58fe2d: [S12] spec setting and getting values of attribute...

2010-09-30 Thread Damian Conway
Moritz wrote: > To re-iterate, Perl 6 has no "real" privacy by default -- both the > default .new and .perl methods give you access to private attributes, > unless you explicitly override them. At least you *can* explicitly override them (and perhaps factor that out into a role that you could alw

Re: [perl6/specs] 58fe2d: [S12] spec setting and getting values of attribute...

2010-09-30 Thread Damian Conway
Carl wrote: > For what it's worth, we had exactly this discussion a couple of days > ago on IRC. I represented your views above, Damian. Thank-you for that. > As long as C<.perl> works the way it does, there can be no real > privacy. Sigh. That is indeed badly broken. Surely it ought to defaul

Re: [perl6/specs] 58fe2d: [S12] spec setting and getting values of attribute...

2010-09-30 Thread Moritz Lenz
Am 30.09.2010 10:32, schrieb Carl Mäsak: Moritz in the spec (>>), Damian (>): After lengthy IRC discussion, we concluded that it's a good idea to provide some form of introspection that doesn't bother about perceived privacy borders, provided that the implementation makes it feasible. Wow, tha

Re: [perl6/specs] 58fe2d: [S12] spec setting and getting values of attribute...

2010-09-30 Thread Carl Mäsak
Moritz in the spec (>>), Damian (>): >> After lengthy IRC discussion, we concluded that it's a good idea to provide >> some form of introspection that doesn't bother about perceived privacy >> borders, provided that the implementation makes it feasible. > > Wow, that's the first time I've ever been

Re: [perl6/specs] 58fe2d: [S12] spec setting and getting values of attribute...

2010-09-30 Thread Damian Conway
On 30 September 2010 06:09, Moritz wrote: > After lengthy IRC discussion, we concluded that it's a good idea to provide > some form of introspection that doesn't bother about perceived privacy > borders, provided that the implementation makes it feasible. Wow, that's the first time I've ever bee

[perl #78142] [BUG] Statement level bare blocks for if statements

2010-09-30 Thread ash
# New Ticket Created by John (ash) # Please include the string: [perl #78142] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=78142 > The S04 section on Statement Level Bare Blocks says: # Not an error: Equivalent to "if fo

[perl6/specs] 66610c: [S12] minor wording tweaks

2010-09-30 Thread noreply
Branch: refs/heads/master Home: http://github.com/perl6/specs Commit: 66610ca4c1bfa509dcb1d6ce0c5c4fcd75234526 http://github.com/perl6/specs/commit/66610ca4c1bfa509dcb1d6ce0c5c4fcd75234526 Author: Carl Masak Date: 2010-09-30 (Thu, 30 Sep 2010) Changed paths: M S12-objects.pod Log Mes