TSa Thomas.Sandlass-at-
This hinges on the details how binding works. If it is pure
name lookup then you can bind only variables of equal type.
But $Larry has the idea of $x1 and $x2 being different views
of the same underlying item. E.g.
That's not at all the same kind of thing as briefly
I'm taking a stab at turning the S\d\d documents into a formal standard.
Going through S02, each factoid gets filed away in a developing
outline. I'm using a single ODT file to make it easy to manipulate the
outline (currently mostly stubs).
Here is an early effort to flesh out imprecise
Thom Boyer thom-at-boyers.org |Perl 6| wrote:
I believe Mr. Stroustrup's deprecation of 'protected' access applies
only to data data members, not function members:
Fortunately, you don't have to use protected data in C++; 'private'
is the default in classes and is usually the better
Larry Wall larry-at-wall.org |Perl 6| wrote:
I only mean that you can't simply rewrite
$foo.($bar)
as
$foo.postcircumfix:( ).($bar)
and think you've gotten anywhere, since you'd then have to rewrite it
again:
$foo.postcircumfix:( ).postcircumfix:( ).($bar)
OK, you got me. What is the ¢ used for? For example, ?{ $¢.pos === $!ws_to
}.
I only see that character as used in this manner (a variable name?), never
defined (e.g. as a variable or parameter) anywhere.
--John
Larry Wall larry-at-wall.org |Perl 6| wrote:
On Wed, Apr 02, 2008 at 06:08:55PM -0700, Jon Lang wrote:
: In Question on your last change to S02, Larry Wall wrote:
: (By the way, you'll note the utility of being able to talk about a
: postfix by saying .[], which is one of the reasons we
What is a list comprehension? I've seen that term bantered around here.
--John
I'm trying to fathom STD.pm.
Maybe someone can help me trace through this one?
How is
$obj!privA = 1;
parsed?
Reading expect_term, it trys noun, then variable sees the $ and commits
to the decision, reads obj as a desigilname, then checks for a ., but
doesn't have similar logic for !.
After reading S12v58, I have many many notes about things that need to
be tightened up or places that open more questions then provide answers.
But, a lot of it boils down to a core set of issues. Can y'all explain
these to me? Help me see the core concepts, and I can work out the
details
chromatic chromatic-at-wgz.org |Perl 6| wrote:
It shouldn't be.
So you are saying that in the example of
class C {
has $.a;
method a ($self:)
{
side_effect();
return $self.a;
}
} # end C
class D is C {
method foo ($self:)
Darren Duncan darren-at-darrenduncan.net |Perl 6| wrote:
A method is defined within a role or class, as is an attribute. A
private attribute can generally be referenced only by a method
declared in the same role or class as said attribute.
I think that's not right. A private attribute
I understand your example. In fact, it further clarifies your earlier note.
But that's not what I meant. I was thinking that access was through a
variable, not understanding the real point of the syntax.
Audrey Tang audreyt-at-audreyt.org |Perl 6| wrote:
John M. Dlugosz wrote:
That seems
not be necessary in all cases? Or should
that passage really say not in non-trusted classes, including derived
classes?
--John
John M. Dlugosz wrote:
OK, trust is not implicit on derived classes. Is that because there is
no rule that says it is, or is there a mention of that somewhere
Ryan Richter ryan-at-tau.solarneutrino.net |Perl 6| wrote:
You've declared method a twice here.
According to S12, You may write your own accessors to override any or all of the
autogenerated ones.
has $!a;
method a { $!a }
The variable is always really the $! form.
I'm catching
Many thanks.
Larry Wall larry-at-wall.org |Perl 6| wrote:
self!BaseName::attr should work, assuming BaseName trusts us.
Because it is an accessor function, not a syntax to reference a variable
in another scope. Got it.
But see my q's to Audrey. Why does it need the qualified name if
If you declare an explicit invocant for an Array type using an array
variable...
Suggest:
The invocant may be given a sigil other than the C$ item sigil using the
same rules as binding variables to class types as described in S02 under Names
and Variables. For example, if the class does the
I just finished another pass on S09v24, and in this posting I note editorial
issues with the file that can easily be corrected. This is as opposed to
subjects for deep discussion, which I'll save for later and individual posts.
= on Mixing subscripts
Within a C.[] indexing operation...
Why the
I understand. Thank you.
This ought to be mentioned in S12. Perhaps after the treatment on my,
explain that our is the default, but saying it explicitly allows the
return type to be first.
--John
Audrey Tang audreyt-at-audreyt.org |Perl 6| wrote:
John M. Dlugosz 提到:
In S29
Larry Wall larry-at-wall.org |Perl 6| wrote:
On Tue, Apr 01, 2008 at 09:27:48PM -0500, John M. Dlugosz wrote:
Having done that before, I find the Perl 6 technical docs to be in relative
disarray and imprecise.
Indeed, I welcome all the help I can get on making things more precise.
My
today.
--John
Audrey Tang audreyt-at-audreyt.org |Perl 6| wrote:
John M. Dlugosz 提到:
= on Parallelized parameters and autothreading
use autoindex;
do { @c[$^i, $^j, $^k, $^l] = @a[$^i, $^j] * @b[$^k, $^l] };
Shouldn't those be semicolons? Ditto for subsequent examples.
Also
Audrey Tang audreyt-at-audreyt.org |Perl 6| wrote:
I guess the wording in the last parenthesized parens is insufficiently
explicit, and maybe we should change it to say that it's really a syntax
error to use placeholder blocks in statement positions. Sounds reasonable?
Cheers,
Audrey
Larry Wall larry-at-wall.org |Perl 6| wrote:
Now, you'll ask how *-2 works. If you do math on a Whatever object,
it just remembers that offset until the Whatever is given a meaning,
which, in this case, is delayed until the subscripting operator
decides what the size of the next dimension is.
Larry Wall larry-at-wall.org |Perl 6| wrote:
At compile time the subscript parser really only knows how
many dimensions are referred to by how many semicolons there
are. A subscript that is explicitly cast to @@ is known to be
multidimensional, and interpolates the returned List of Capture into
#[ are there people paying attention to these issues on other mailing lists? ]
= on Compact structs
revision 1, initial posting
What functions serialize/deserialize to the C view?
If these are to be member functions, they would be applicable only if the
struct is compact, and erroneous to call
Brandon S. Allbery KF8NH allbery-at-ece.cmu.edu |Perl 6| wrote:
$stream.print (Buf $record);
$stream.print($record.pack) # I would think?
Thank you so much for the reply. I was beginning to wonder if Perl 6
interest is dead, or if there is another secret lair for current
enthusiasts
, 2008 at 12:25:50PM -0500, John M. Dlugosz wrote:
Thank you so much for the reply. I was beginning to wonder if Perl 6
interest is dead, or if there is another secret lair for current
enthusiasts that I'm unaware of.
Sorry, many of us have to live under budgetary constraints of time
In S29, there are definitions like
our Capture method shape (@array: ) is export
But in S12 there is no mention as to what an our method is. It states that
my is used to make private methods, and ^ to make class methods.
I think this is a doc relic and should be fixed globally in that
TSa Thomas.Sandlass-at-barco.com |Perl 6| wrote:
Now my question: could slice context be a runtime feature that acts
before the dispatch to postcircumfix:[ ] by retrieving the shape
of the @array and handing it over to foo as context, capture the
shape of the slice returned and hand over the
From: Agent Zhang
IMHO pod2html is old and broken in various ways. I think you should
use the tools provided by Pod::Simple instead. For the Synopses on
feather, we're using the podhtml.pl script (based on
Pod::Simple::HTML):
http://svn.pugscode.org/pugs/util/podhtm.pl
Hopefully you
The context in which a subscript is evaluated is no longer controlled
by the sigil either. Subscripts are always evaluated in list context.
+(More specifically, they are evaluated in a variant of list context
+known as Islice context, which preserves dimensional information
+so that you can do
In S02, If a buf type is initialized with a Unicode string value, the string
is decomposed into Unicode codepoints,...If any other conversion is desired, it
must be specified explicitly.
In S29, there is nothing about functions in Buf, and nothing about functions
that convert or initialize
I've read copies of the Synopsis documents that I've found on the web
somewhere. How do I synchronize with the life copies, and hack on them?
--John
I've installed the Win32 build of Pugs, but is appears to be incomplete. How
do I get the real thing? I've also heard that Pugs is in stasis, so is this
still a good way to write stuff and learn today?
Likewise, how do I get synched up with the Parrot implementation? I understand
the most
I'm reading S02.pod with version information:
Last Modified: 17 Mar 2008
Number: 2
Version: 130
Meta-question 1: what is the succinct way to report this? Is the Version 130
enough?
Meta-question 2: Does this belong on a different mailing list? I'm also
including the documented file
Any contiguous whitespace (including comments) may be hidden from the parser
by prefixing it with code\/code. ... using unspace lets you line up postfix
operators:
%hash\ .{$key}
@array\ .[$ix]
$subref\.($arg)
What does the dotted form have to do with this? It just confuses the
301 - 335 of 335 matches
Mail list logo
