Author: allison
Date: Thu Aug 28 02:02:51 2008
New Revision: 30616
Added:
trunk/docs/pdds/draft/pdd30_install.pod
Log:
[pdd] Adding a draft installation PDD, thanks to Reini Urban.
Added: trunk/docs/pdds/draft/pdd30_install.pod
Reini Urban wrote:
I have one more draft.
chromatic told me write up such a thing, but it's not finished yet.
It could go to the cygwin070patches branch which is really a
parrot_install branch, but also to HEAD.
This needs some technical review because but I'm still a beginner
in what is
Reini Urban wrote:
+=head1 DESCRIPTION
+
+Parrot installation mechanisms are more powerful than perl5's.
+MANIFEST contains also the end location, tools/dev/install_files.pl is driven
+by this definition.
To me it's not clear what the end location is - care to elaborate?
Moritz
--
Moritz
NotFound wrote:
Hello.
The current grammar for ATTR in pmc2c allows declarations of the form:
type * varname
In the perl6multisub pmc we have the attribute candidates_sorted whose
intended type is candidate_info **, having two problems:
The current grammar allows a single pointer, not a
Author: Whiteknight
Date: Wed Aug 27 16:25:00 2008
New Revision: 30604
Modified:
trunk/docs/pdds/draft/pdd11_extending.pod
Changes in other areas also in this revision:
Modified:
trunk/src/extend.c
trunk/src/inter_run.c
Log:
[DOCS] Document Parrot_call_method as per RT#36243. Also,
On Thu Oct 25 00:49:38 2007, pcoch wrote:
To be totally honest I wish I knew. I'm just going through converting
the todo items in code into RT tickets and sometimes the todo comments
aren't necessarily all that clear as to what needs to be done. I'm
also (unfortunately) not familiar enough
# New Ticket Created by Allison Randal
# Please include the string: [perl #58414]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=58414
Briefly discussed in a phone call with Patrick, Jerry, and chromatic:
Our
# New Ticket Created by Allison Randal
# Please include the string: [perl #58410]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=58410
Briefly discussed on the phone with Patrick, Jerry, and chromatic: The
versions
2008/8/28 Moritz Lenz [EMAIL PROTECTED]:
+=head1 DESCRIPTION
+
+Parrot installation mechanisms are more powerful than perl5's.
+MANIFEST contains also the end location, tools/dev/install_files.pl is
driven
+by this definition.
To me it's not clear what the end location is - care to
On Thu, Aug 28, 2008 at 11:33 AM, Allison Randal [EMAIL PROTECTED] wrote:
Approved for application. But, keep in mind that ATTRs other than INTVAL,
FLOATVAL, STRING *, and PMC * cannot have automatic GET_ATTR/SET_ATTR
accessor macros generated for them, and any C PMCs with these low-level
Reini Urban wrote:
2008/8/28 Moritz Lenz [EMAIL PROTECTED]:
+=head1 DESCRIPTION
+
+Parrot installation mechanisms are more powerful than perl5's.
+MANIFEST contains also the end location, tools/dev/install_files.pl is
driven
+by this definition.
To me it's not clear what the end location
2008/8/28 Moritz Lenz [EMAIL PROTECTED]:
Reini Urban wrote:
2008/8/28 Moritz Lenz [EMAIL PROTECTED]:
+=head1 DESCRIPTION
+
+Parrot installation mechanisms are more powerful than perl5's.
+MANIFEST contains also the end location, tools/dev/install_files.pl is
driven
+by this definition.
On Thu, Aug 28, 2008 at 02:10:27PM +0200, Reini Urban wrote:
Open problem:
For language pbc's a new dir like script_dir or lib_dir/parrot/bin
would be required.
They could also pollute $(DESTDIR)@lib_dir@/parrot/library where the other
pbc's are.
The language group and op shared libs go to
On Tue, 26 Aug 2008, James Keenan via RT wrote:
Patched two subs in Parrot::Configure and adjusted test files in r30583.
Tested with triggers in hints files on Linux and Darwin.
Thanks. That closes this ticket and just leaves us with the old familiar:
Two other items that ought to be taken into consideration:
- We need an implementation of the :lookahead flag for Rakudo.
(See discussion thread at [1].)
- Per a conversation with Allison and Jonathan at YAPC::EU, it might
be useful to have a :capture flag on parameters and return
2008/8/28 Patrick R. Michaud [EMAIL PROTECTED]:
On Thu, Aug 28, 2008 at 02:10:27PM +0200, Reini Urban wrote:
Open problem:
For language pbc's a new dir like script_dir or lib_dir/parrot/bin
would be required.
They could also pollute $(DESTDIR)@lib_dir@/parrot/library where the other
pbc's
Author: allison
Date: Thu Aug 28 09:09:48 2008
New Revision: 30620
Added:
trunk/docs/pdds/draft/pdd31_hll_interop.pod
Log:
[pdd] Adding an early draft PDD for HLL interoperability, from Bob Rogers.
Added: trunk/docs/pdds/draft/pdd31_hll_interop.pod
[EMAIL PROTECTED] wrote:
+{{ Is the term unimethod acceptable here? -- rgr, 29-Jul-08. }}
I think for dispatch the term is single dispatch, and unimethod
could thus be single method.
Moritz
--
Moritz Lenz
http://moritz.faui2k3.org/ | http://perl-6.de/
On Thu, 2008-08-28 at 00:03 -0700, Allison Randal wrote:
Briefly discussed on the phone with Patrick, Jerry, and chromatic: The
versions of the math opcodes that modify an existing destination PMC
instead of creating a new destination PMC are not useful to HLLs,
because they make
On Thu, Aug 28, 2008 at 11:09 AM, Reini Urban [EMAIL PROTECTED] wrote:
2008/8/28 Patrick R. Michaud [EMAIL PROTECTED]:
On Thu, Aug 28, 2008 at 02:10:27PM +0200, Reini Urban wrote:
Open problem:
For language pbc's a new dir like script_dir or lib_dir/parrot/bin
would be required.
They could
Will Coleda schrieb:
On Thu, Aug 28, 2008 at 11:09 AM, Reini Urban [EMAIL PROTECTED] wrote:
We could thing of symlinking it to runtime/parrot/library
at make languages, so language_interop can be tested.
Are symlinks usable wherever we might install?
True, there's no perl
François Perrad schrieb:
The following patch adds NCIGEN in the documentation (HTML generated).
Note : needs a better title than 'Native Call Interface Generator'.
Why?
I find it perfect.
It makes sense and it even matches the abbrevation.
Java:
Java native interface code generator
Bob Rogers wrote:
OK, here's my straw-man proposal for a language interoperability
framework; my apologies for sitting on it so long. It's still pretty
messy, but I'm sure it will benefit more from other viewpoints at this
stage than from polishing.
Thanks, added to trunk as
Will Coleda schrieb:
On Sun, Aug 24, 2008 at 12:26 PM, Moritz Lenz
[EMAIL PROTECTED] wrote:
Reini Urban wrote:
2008/8/23 François Perrad [EMAIL PROTECTED]:
2008/8/23 Allison Randal [EMAIL PROTECTED]:
Moritz Lenz wrote:
On #perl6 somebody just asked if there were up-to-date windows builds of
On Thu, 28 Aug 2008, Reini Urban wrote:
Will Coleda schrieb:
On Thu, Aug 28, 2008 at 11:09 AM, Reini Urban [EMAIL PROTECTED] wrote:
We could thing of symlinking it to runtime/parrot/library
at make languages, so language_interop can be tested.
Are symlinks usable wherever we might
On Thu, Aug 28, 2008 at 2:37 PM, Reini Urban [EMAIL PROTECTED] wrote:
Will Coleda schrieb:
On Sun, Aug 24, 2008 at 12:26 PM, Moritz Lenz
[EMAIL PROTECTED] wrote:
Reini Urban wrote:
2008/8/23 François Perrad [EMAIL PROTECTED]:
2008/8/23 Allison Randal [EMAIL PROTECTED]:
Moritz Lenz
Allison Randal wrote:
Bob Rogers wrote:
OK, here's my straw-man proposal for a language interoperability
framework; my apologies for sitting on it so long. It's still pretty
messy, but I'm sure it will benefit more from other viewpoints at this
stage than from polishing.
Thanks, added to
Author: allison
Date: Thu Aug 28 12:43:19 2008
New Revision: 30622
Modified:
trunk/docs/pdds/draft/pdd31_hll_interop.pod
Log:
[pdd] Adding a series of architectural comments to the HLL Interop PDD.
Modified: trunk/docs/pdds/draft/pdd31_hll_interop.pod
[EMAIL PROTECTED] wrote:
Opcode names are not reserved words in PIR, and may be used as variable names.
For example, you can define a local variable named Cprint. [See RT #24251]
+Note that by using an opcode name as a local variable name, the variable will
+Ihide the opcode name, effectively
Moritz Lenz wrote:
[EMAIL PROTECTED] wrote:
+{{ Is the term unimethod acceptable here? -- rgr, 29-Jul-08. }}
I think for dispatch the term is single dispatch, and unimethod
could thus be single method.
Just single dispatch. A method that's single dispatched, is... a method.
Allison
Reini Urban schrieb:
Moritz Lenz schrieb:
Reini Urban wrote:
My latest patch against the cygwin070patches branch r30596.
And one more.
pdd30_install.pod, silence Parrot/Configure/Compiler.pm, more testcases,
parrot_config, $(SHRPENV) $(MINIPARROT) for the last missing build problem.
Add
[EMAIL PROTECTED] wrote:
+PIR keywords, on the other hand, Iare reserved, and cannot be used as
+identifiers. Some opcode names (Cif, Cunless) are, in fact, PIR keywords,
+which therefore cannot be used as identifiers.
If the PDD says the keywords are reserved, it also needs to say what the
Andy Dougherty schrieb:
On Thu, 28 Aug 2008, Reini Urban wrote:
Will Coleda schrieb:
On Thu, Aug 28, 2008 at 11:09 AM, Reini Urban [EMAIL PROTECTED] wrote:
We could thing of symlinking it to runtime/parrot/library
at make languages, so language_interop can be tested.
Are symlinks usable
Reini Urban wrote:
A new idea:
===
#IF(darwin):
#ALSO:# MACOSX_DEPLOYMENT_TARGET must be defined for OS X
#ALSO:export MACOSX_DEPLOYMENT_TARGET := @osx_version@
Just a little too much complexity, for not enough benefit.
The POD for this change:
Looks good.
For legacy the old
Will Coleda wrote:
At the moment I'm planning for language pbcs to go into
.../parrot/library/ so they can be easily accessed via
load_bytecode. I've found that in a dynamic environment like
Parrot there's very little difference between a language and
a library [1]. :-)
That's probably the
On Thu, Aug 28, 2008 at 11:10:47PM +0200, Allison Randal wrote:
That's backwards. Loading the language module is what registers the
compiler. The user never needs to access the compiler object for a
particular language directly unless they're compiling code from a string.
...or if they
Patrick R. Michaud wrote:
On Thu, Aug 28, 2008 at 11:10:47PM +0200, Allison Randal wrote:
That's backwards. Loading the language module is what registers the
compiler. The user never needs to access the compiler object for a
particular language directly unless they're compiling code from a
From: Allison Randal [EMAIL PROTECTED]
Date: Thu, 28 Aug 2008 22:14:08 +0200
Moritz Lenz wrote:
[EMAIL PROTECTED] wrote:
+{{ Is the term unimethod acceptable here? -- rgr, 29-Jul-08. }}
I think for dispatch the term is single dispatch, and unimethod
could thus be
This dependence has been eliminated from 20 of the 76 current
configuration step tests. More to come.
kid51
Marking ticket resolved.
No complaints in five days. No smolder test failures. Marking ticket
resolved.
No objections so far. If I hear none, I will apply this patch this weekend.
42 matches
Mail list logo
