n 2016)
Changed paths:
M S22-package-format.pod
Log Message:
---
META doesn't need an entire glossary to itself
There's a document-level one right above it. Merged the two.
v 2015)
Changed paths:
M S99-glossary.pod
Log Message:
---
Add "XS" to glossary
paths:
M S99-glossary.pod
Log Message:
---
Add "list to remember" to glossary
paths:
M S99-glossary.pod
Log Message:
---
Define CURLI in glossary
)
Changed paths:
M S99-glossary.pod
Log Message:
---
pouring into the glossary Danaides barrel
paths:
M S99-glossary.pod
Log Message:
---
Correcting misplaced section links in glossary
Commit: 3de429d4c8b2c7ef3606f3b6c492787daf9059c6
https://github.com/perl6/specs/commit/3de429d4c8b2c7ef3606f3b6c492787daf9059c6
Author: Paul Cochrane p...@liekut.de
Date: 2015
paths:
M S99-glossary.pod
Log Message:
---
Resolving unresolved internal links in glossary
Commit: 44a21c0439101276cd9e43ac6eb2d4af6562da97
https://github.com/perl6/specs/commit/44a21c0439101276cd9e43ac6eb2d4af6562da97
Author: Paul Cochrane p...@liekut.de
Date: 2015
paths:
M S99-glossary.pod
Log Message:
---
glossary: Add an example for an infix
paths:
M S99-glossary.pod
Log Message:
---
More glossary updates (Synopsis, TMTOWTDI)
paths:
M S99-glossary.pod
Log Message:
---
[glossary] explain thunk
paths:
M S99-glossary.pod
Log Message:
---
Add some more glossary terms
paths:
M S99-glossary.pod
Log Message:
---
more glossary entries
)
Changed paths:
A S99-glossary.pod
Log Message:
---
Framework for a Perl 6 glossary
# New Ticket Created by Matt Kraai
# Please include the string: [perl #60658]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=60658
Howdy,
On the Developer Resources page at http://www.parrot.org/dev, the
Glossary
# New Ticket Created by Zev Benjamin
# Please include the string: [perl #49902]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=49902
May as well mention what Rakudo is in the glossary entry.
Zev
Index: languages
applied with minor modifications as r24966.
~jerry
hi,
on
http://www.parrotcode.org/resources.html
there's a link named glossary.
clicking on that link results in an empty page. The glossary is in
docs/glossary.pod
It should be put it in the website repository too.
regards,
kjs
, 2007 6:34:06 AM EST
To: Perl 6 Internals perl6-internals@perl.org
Subject: Glossary is missing from parrotcode.org
hi,
on
http://www.parrotcode.org/resources.html
there's a link named glossary.
clicking on that link results in an empty page. The glossary is in
docs/glossary.pod
On Jul 2, 2006, at 11:23 PM, Uri Guttman wrote:
hi to all docathon hackers (and others too),
one idea we came up with during the docathon is that perl6 needs a
glossary. would the terms autobox or mixin make any sense to a newcomer
who didn't know any OO theory? so this is a proposal
]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Uri
Guttman
Sent: Sunday, July 02, 2006 5:24 PM
To: perl6-language@perl.org
Cc: [EMAIL PROTECTED]
Subject: [yapc] DOC: glossary
hi to all docathon hackers (and others too),
one idea we came up with during
hi to all docathon hackers (and others too),
one idea we came up with during the docathon is that perl6 needs a
glossary. would the terms autobox or mixin make any sense to a newcomer
who didn't know any OO theory? so this is a proposal to start a glossary
as a new S\d+ or other document. here
I haven't actually read your message, just the Subject, because I was
just going to bed.
Be sure to check out http://pugs.kwiki.org/?Perl6Nomenclature
Juerd
--
http://convolution.nl/maak_juerd_blij.html
http://convolution.nl/make_juerd_happy.html
http://convolution.nl/gajigu_juerd_n.html
Parrotcode's TODO list
http://www.parrotcode.org/todo.html
Has a reference to the glossary.pod. I presume this was supposed to be reference to
the TODO file in the source, which, pending another patch, is now empty. This patch
removes the ref to the TODO file instead of updating it.
(I saw a
I just committed a few new glossary entries for folks reading
the summaries: IMC, IMCC, Packfile, PBC, PIR.
--
Gregor Purdy[EMAIL PROTECTED]
Focus Research, Inc. http://www.focusresearch.com/
On 11/17/2002 1:11 AM, Dave Storrs wrote:
Arrays know how to manage their own size; they will grow and shrink as
needed when you add or remove elements. You never need to worry about
whether an array has enough space to hold the number of elements you
are about to insert.
Reference to
James Mastros wrote:
On 11/17/2002 1:11 AM, Dave Storrs wrote:
Arrays know how to manage their own size; they will grow
and shrink as needed when you add or remove elements. You
never need to worry about whether an array has enough space
to hold the number of elements you are about to
On Tue, Nov 26, 2002 at 08:38:55AM -0600, Garrett Goebel wrote:
: James Mastros wrote:
: On 11/17/2002 1:11 AM, Dave Storrs wrote:
: Arrays know how to manage their own size; they will grow
: and shrink as needed when you add or remove elements. You
: never need to worry about whether an
From: Dave Storrs [mailto:[EMAIL PROTECTED]]
On Thu, Nov 14, 2002 at 02:29:38PM -0600, Garrett Goebel wrote:
It is interesting that no one has yet taken the time to
start defining the terms we're using.
Good point. I volunteered to be keeper of the glossary a while ago,
but I never
Dave Storrs writes:
Good point. I volunteered to be keeper of the glossary a while ago,
but I never actively started creating one. That said, let's make this
the first entry. Comments and constructive criticisms welcomed from
all comers.
I tryed to cut in stone ( but this is very
=-
=section assignment vs binding
=-
* A = B ;
assign means :
evaluate the *value* on the right hand side and
*distribute* it ( value ) among the containers ( which if
terminology clearing :
=back
=over glossary
=item * variable -
a variable-name associated with ( referencing )
container.
=item * variable-name -
an entry in the symbol-table that contains a name
- string beginning with *sigil* . otherwize
On Thu, Nov 14, 2002 at 02:29:38PM -0600, Garrett Goebel wrote:
It is interesting that no one has yet taken the time to start defining the
terms we're using.
Good point. I volunteered to be keeper of the glossary a while ago,
but I never actively started creating one. That said, let's make
Stéphane Payrard wrote:
On (14/11/02 16:21), Garrett Goebel wrote:
Stéphane Payrard wrote:
But when we say literal array, do we talk about the representation
or the value?
The representation of a fixed value.
If a literal is the representation of a constant value,
then a
It is interesting that no one has yet taken the time to start defining the
terms we're using.
For instance what is a literal?
Would everyone agree with the following definition?
A literal is the represention of a constant value. It is important not to
confuse the representation with the value.
On (14/11/02 14:29), Garrett Goebel wrote:
From: Garrett Goebel [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Glossary?
Date: Thu, 14 Nov 2002 14:29:38 -0600
It is interesting that no one has yet taken the time to start defining the
terms we're using.
For instance what is a literal
Stéphane Payrard wrote:
On (14/11/02 14:29), Garrett Goebel wrote:
It is interesting that no one has yet taken the time to
start defining the terms we're using.
For instance what is a literal?
Would everyone agree with the following definition?
A literal is the represention
On (14/11/02 16:21), Garrett Goebel wrote:
From: Garrett Goebel [EMAIL PROTECTED]
To: 'Stéphane Payrard' [EMAIL PROTECTED],
Garrett Goebel [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: Glossary?
Date: Thu, 14 Nov 2002 16:21:23 -0600
Stéphane Payrard wrote:
On (14/11/02 14
it in the glossary, so here is an explanation and a link.
-kevin
diff -u -p -r1.6 glossary.pod
--- glossary.pod26 Aug 2002 03:02:26 - 1.6
+++ glossary.pod3 Sep 2002 13:30:04 -
-152,7 +152,18 objects faster than memory)
See also: LDOD
+=head2 ICU
Hi all,
I've been lurking for a bit until I'm up to speed enough to help out. I'm glad to see
a glossary is forming of some of the terms newbies need, but there are some things I
think are missing.
First is that COW was discussed a few days (weeks?) ago, but doesn't appear to have
made
At 11:13 AM 7/12/2002 -0400, Mike Litherland wrote:
I've been lurking for a bit until I'm up to speed enough to help out. I'm
glad to see a glossary is forming of some of the terms newbies need, but
there are some things I think are missing.
First is that COW was discussed a few days (weeks
? There may already be something
there. The glossary is probably a good idea anyway.
It's not in there. Looks from the website source that the glossary
page is build from docs/glossary.pod. I'll update it now with COW,
GC, DOD, and PMC.
PS Other website updates:
Aren't we on version 0.0.6 now
At 12:01 PM -0400 7/12/02, Melvin Smith wrote:
Did you check docs/ and docs/pdds first? There may already be something
there. The glossary is probably a good idea anyway.
I added some definitions to glossary. I think the changes'll be
picked up on parrotcode.org around 4PM EST
Dan Sugalski writes:
At 12:01 PM -0400 7/12/02, Melvin Smith wrote:
Did you check docs/ and docs/pdds first? There may already be something
there. The glossary is probably a good idea anyway.
I added some definitions to glossary. I think the changes'll be
picked up on parrotcode.org around 4PM
At 10:27 AM -0700 7/12/02, Robert Spier wrote:
Dan Sugalski writes:
At 12:01 PM -0400 7/12/02, Melvin Smith wrote:
Did you check docs/ and docs/pdds first? There may already be something
there. The glossary is probably a good idea anyway.
I added some definitions to glossary. I think
I've heard reports of rsync not working. I don't use it, so I dunno
there. If someone's got the proper incantation, or follows the
directions and it doesn't work (when you're *sure* you know what
you're doing) I'll update it appropriately.
Yes, this seems broken at the moment. I've opened a
Correct, I don't maintain the site, but I believe Robert has said he would
accept patches.
Yes, if people send me updates/diff/new content's, or just replace
this paragraph with this, I'll do the merges.
-R
[EMAIL PROTECTED] (Robert Spier) writes:
I've heard reports of rsync not working. I don't use it, so I dunno
there. If someone's got the proper incantation, or follows the
directions and it doesn't work (when you're *sure* you know what
you're doing) I'll update it appropriately.
Yes,
FYI; the Guile schemers have had several discussions that may be of
interest to the Parrot personnel regarding copy on write strings and
shared substrings. Perhaps they thought of something you have not? I
imagine they must have a list archive you can find.
--
As any limb well and duly
Markus Laire wrote:
I've been following this list for a month, but havn't yet learned what COW
really means. It's used so often that perhaps it should be added to Parrot
Glossary.
I'll give my try, but I'm no expert at all. feel free to correct me if I'm
wrong.
COW stands for Copy On Write
On Fri, 5 Jul 2002, Nicholas Clark wrote:
: On Fri, Jul 05, 2002 at 02:54:18PM +0200, Aldo Calpini wrote:
: this approach saves memory, because you can create as many copies of a
: string as you want, without allocating it many times. unless you modify
: them, at least. it's also usually a
The glossary in cvs docs/glossary.pod is now available on the web:
http://www.parrotcode.org/glossary
There's enough words and definitions going by that not everyone
understands that it's time for us to have a glossary.
I'm willing to do the administrative work of maintaining it, if others
send me entries.
So... if there are words you think should be in the parrot glossary
(the recent
52 matches
Mail list logo
