Re: [PATCH 1/6] [library] Test::More: use hllmacros.pir in man page example

Sam Vilain wrote: Will Coleda wrote: FYI, all six patches were just opened as tickets. 41809 is a dup of 41803 41810 is a dup of 41804 41811 is a dup of 41805 41812 is a dup of 41807 41813 is a dup of 41806 These have all been applied and resolved, or rejected. Thanks, Allison

[perl #41808] [PATCH 1/6] [library] Test::More: use hllmacros.pir in man page example

Namespaces have an export feature. A bit clunky, but a definite improvement over the .IMPORT macro. I've replaced all instances of .IMPORT with the "export_to" method, except languages/PIR/examples/test.pir, because it seems to just be a generic syntax example.

[perl #41808] [PATCH 1/6] [library] Test::More: use hllmacros.pir in man page example

# New Ticket Created by Sam Vilain # Please include the string: [perl #41808] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=41808 > Use current best practice for importing symbols in the example. --- runtime/parrot/libra

Re: [PATCH 1/6] [library] Test::More: use hllmacros.pir in man page example

Will Coleda wrote: > FYI, all six patches were just opened as tickets. > 01:33 <@Coke> do me a favor. Forward each of them to RT and open a ticket. HA! I followed this instruction, "moments" before you forwarded them. Where "moments" is a time period defined by the perl.org mailserver. So, 41

Re: [PATCH 1/6] [library] Test::More: use hllmacros.pir in man page example

FYI, all six patches were just opened as tickets. I marked this on the ticket for 1/6 and it's closed out. the rest await a ruling. On Mar 13, 2007, at 2:17 PM, Allison Randal wrote: I know I started the spread of the .IMPORT macros through the PIR- based test files while I was working with

Re: [PATCH 1/6] [library] Test::More: use hllmacros.pir in man page example

I know I started the spread of the .IMPORT macros through the PIR-based test files while I was working with Sam on the SMOP prototype, but when I see sane, maintainable code using a documented interface like "find_global", replaced with a cryptic hackish macro (e.g. passing in the '_' variable

[PATCH 1/6] [library] Test::More: use hllmacros.pir in man page example

Use current best practice for importing symbols in the example. --- runtime/parrot/library/Test/More.pir | 26 -- 1 files changed, 12 insertions(+), 14 deletions(-) diff --git a/runtime/parrot/library/Test/More.pir b/runtime/parrot/library/Test/More.pir index 8441b25..5

[PATCH 1/6] [library] Test::More: use hllmacros.pir in man page example

Use current best practice for importing symbols in the example. --- runtime/parrot/library/Test/More.pir | 26 -- 1 files changed, 12 insertions(+), 14 deletions(-) diff --git a/runtime/parrot/library/Test/More.pir b/runtime/parrot/library/Test/More.pir index 8441b25..