Re: pm6 naming convention

On 2/12/24 15:04, Will Coleda wrote: On Mon, Feb 12, 2024 at 5:32 PM ToddAndMargo via perl6-users mailto:perl6-us...@perl.org>> wrote: On 2/12/24 14:29, ToddAndMargo via perl6-users wrote: >>> On Mon, Feb 12, 2024 at 3:24 PM ToddAndMargo via perl6-users >>> mailto:perl6-us...@p

Re: pm6 naming convention

On 2/12/24 15:04, Will Coleda wrote: Pull requests welcome, and if you have any specific notes about searches that aren't working for you, please report them on https://github.com/Raku/doc/issues . You can click on the edit icon on that doc page to easily su

Re: pm6 naming convention

On Mon, Feb 12, 2024 at 5:32 PM ToddAndMargo via perl6-users < perl6-us...@perl.org> wrote: > On 2/12/24 14:29, ToddAndMargo via perl6-users wrote: > >>> On Mon, Feb 12, 2024 at 3:24 PM ToddAndMargo via perl6-users > >>> mailto:perl6-us...@perl.org>> wrote: > >> > >>> Has .pl6 been renamed too

Re: pm6 naming convention

On 2/12/24 14:29, ToddAndMargo via perl6-users wrote: On Mon, Feb 12, 2024 at 3:24 PM ToddAndMargo via perl6-users mailto:perl6-us...@perl.org>> wrote:     Has .pl6 been renamed too? On 2/12/24 12:37, Will Coleda wrote: > Please see: https://docs.raku.org/language/filename-extensions >

Re: pm6 naming convention

On Mon, Feb 12, 2024 at 3:24 PM ToddAndMargo via perl6-users mailto:perl6-us...@perl.org>> wrote: Has .pl6 been renamed too? On 2/12/24 12:37, Will Coleda wrote: > Please see: https://docs.raku.org/language/filename-extensions > > Than

Re: pm6 naming convention

>> > >>>> The file transfer portion, which I adore, posts a Microsoft > >>>> Office Publisher Icon (a big one) when it hits a .pm6 modules. > >>>> > >>>> Is there a different naming convention I can use for my > >>>> m

Re: pm6 naming convention

one) when it hits a .pm6 modules. Is there a different naming convention I can use for my modules that does not mimic some other program? Many thanks, -T On 2/12/24 11:11, Elizabeth Mattijsen wrote: .rakumod Thank you! Is there a way to get raku to ignore pm (perl 5) module naming? On 2/12

Re: pm6 naming convention

;>> I use AnyDesk for remoter customer support. Work rather well. >>> >>> The file transfer portion, which I adore, posts a Microsoft >>> Office Publisher Icon (a big one) when it hits a .pm6 modules. >>> >>> Is there a different naming convention I c

Re: pm6 naming convention

convention I can use for my modules that does not mimic some other program? Many thanks, -T On 2/12/24 11:11, Elizabeth Mattijsen wrote: > .rakumod Thank you! Is there a way to get raku to ignore pm (perl 5) module naming?

Re: pm6 naming convention

its a .pm6 modules. > > Is there a different naming convention I can use for my > modules that does not mimic some other program? > > Many thanks, > -T > > -- > ~~ > Computers are like air conditioners. > They malfunction when you open windows > ~~

pm6 naming convention

Hi All, I use AnyDesk for remoter customer support. Work rather well. The file transfer portion, which I adore, posts a Microsoft Office Publisher Icon (a big one) when it hits a .pm6 modules. Is there a different naming convention I can use for my modules that does not mimic some other

[perl6/specs] acc747: Be more specific about coercion being a convention

S13-overloading.pod Log Message: --- Be more specific about coercion being a convention

Re: [perl #41623] [TODO] modify p6regex op naming convention to match perl 6

his issue. : > # http://rt.perl.org/rt3/Ticket/Display.html?id=41623 > : > : > : > pge's syntax for specifying ops to the op precedence parser should : > follow the perl 6 spec in it's op rule naming convention. that is, : > 'infix:+' : > 'circumf

[perl #41623] [TODO] modify p6regex op naming convention to match perl 6

l 6 spec in it's op rule naming convention. that is, 'infix:+' 'circumfix:( )' should be infix:<+> circumfix:<( )> ~jerry

Re: [perl #41623] [TODO] modify p6regex op naming convention to match perl 6

; > pge's syntax for specifying ops to the op precedence parser should > follow the perl 6 spec in it's op rule naming convention. that is, > 'infix:+' > 'circumfix:( )' > > should be > infix:<+> > circumfix:<( )> We s

[perl #41217] [BUG] warnings in refactored calling convention code (src/inter_call.c)

# New Ticket Created by Jerry Gay # Please include the string: [perl #41217] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=41217 > src\inter_call.c src\inter_call.c(255) : warning C4098: 'fetch_arg_sig' : 'void' function r

Re: [Fwd: [perl6.internals] Re: [PROPOSAL] calling convention abstraction]

r response from you. The subject of the thread was "calling convention abstraction". My proposal was about one possible way to go, and I'd like to thank you for the input. But there is much more then the one discussed issue. I'd like to have HLL folks create a workable schem

Re: [PROPOSAL] calling convention abstraction

Bob Rogers wrote: So it sounds like we are all saying the same thing now? Well, two of us at least (with me coming from the peanut gallery)... Leo has his own say, and it's his proposal. regards, Roger

Re: [PROPOSAL] calling convention abstraction

From: Roger Hale <[EMAIL PROTECTED]> Date: Mon, 11 Apr 2005 09:30:32 -0400 Bob Rogers wrote: >From: Roger Hale <[EMAIL PROTECTED]> >Date: Thu, 07 Apr 2005 04:23:41 -0400 > >Leopold Toetsch wrote: >> Roger Hale <[EMAIL PROTECTED]> wrote: >> >>

Re: [PROPOSAL] calling convention abstraction

Bob Rogers wrote: From: Roger Hale <[EMAIL PROTECTED]> Date: Thu, 07 Apr 2005 04:23:41 -0400 Leopold Toetsch wrote: > Roger Hale <[EMAIL PROTECTED]> wrote: > >>Leopold Toetsch wrote: >> >>>As @ARGS (or @IN_ARGS, @OUT_ARGS) is being stored in the context, and >>>that cont

Re: [PROPOSAL] calling convention abstraction

From: Roger Hale <[EMAIL PROTECTED]> Date: Thu, 07 Apr 2005 04:23:41 -0400 Leopold Toetsch wrote: > Roger Hale <[EMAIL PROTECTED]> wrote: > >>Leopold Toetsch wrote: >> >>>As @ARGS (or @IN_ARGS, @OUT_ARGS) is being stored in the context, and >>>that context is defacto th

Re: [PROPOSAL] calling convention abstraction

Leopold Toetsch wrote: Roger Hale <[EMAIL PROTECTED]> wrote: Leopold Toetsch wrote: As @ARGS (or @IN_ARGS, @OUT_ARGS) is being stored in the context, and that context is defacto the continuation, yes - a tail-call would inherit this information. But as each tail-call supplies a new @ARGS, how can

Re: [PROPOSAL] calling convention abstraction

Roger Hale <[EMAIL PROTECTED]> wrote: > Leopold Toetsch wrote: >> >> As @ARGS (or @IN_ARGS, @OUT_ARGS) is being stored in the context, and >> that context is defacto the continuation, yes - a tail-call would >> inherit this information. >> >> leo > But as each tail-call supplies a new @ARGS, how c

Re: [PROPOSAL] calling convention abstraction

Leopold Toetsch wrote: Roger Hale <[EMAIL PROTECTED]> wrote: Leopold Toetsch wrote: sub foo { want.List ?? (1,2,3) :: 1 } # or some such This information could also be attached to @ARGS. E.g. @ARGS."return_list"(1) Would it be possible to attach it to the continuation? Then in the course of

Re: [PROPOSAL] calling convention abstraction

Roger Hale <[EMAIL PROTECTED]> wrote: > Leopold Toetsch wrote: > > sub foo { want.List ?? (1,2,3) :: 1 } # or some such > > > > This information could also be attached to @ARGS. E.g. > > > > @ARGS."return_list"(1) > Would it be possible to attach it to the continuation? Then in the > cours

Re: [PROPOSAL] calling convention abstraction

Leopold Toetsch wrote: Below inline attached is a scheme for an abstraction layer around calling conventions. Comments welcome, leo > 2.5) return context > > Yesterdays conversation on IRC (yes!) has clearly shown that the > current calling conventions are lacking information about scalar vs > li

[PROPOSAL] calling convention abstraction

Below inline attached is a scheme for an abstraction layer around calling conventions. Comments welcome, leo Parrot Calling Conventions 1) Rational Calling conventions and opcodes (and of course the semantics of these) define the ABI of the Parrot VM. Any change in the ABI creates incompatibili

Re: [PATCH: P6C] update calling convention

Dan Sugalski wrote: > > Might not be out of line to start a notes file or something to throw > in observations and whatnot that you and other folks come across as > you work on this stuff. I just added languages/perl6/doc/developer_notes.pod, with a few current notes. Add to it as relevant. Alli

Re: [PATCH: P6C] update calling convention

On May-09, Allison Randal wrote: > > BTW, should I keep working on P6C? As A12 has just come out P6C may be > > heavily under construction, and I don't want to be in the way... > > Please do. I'm working on a first rough implementation of classes, but > it shouldn't interfere with general patches.

Re: [PATCH: P6C] update calling convention

Allison Randal <[EMAIL PROTECTED]> wrote: > If syntax like this: > find_lex $P2, "&die" > $P2($P0) > isn't possible yet, it probably should be. Works since some weeks. > Allison leo

Re: [PATCH: P6C] update calling convention

Abhijit A. Mahabal wrote: > this is my first patch ever (not just p6i: ever). So do tell me > what I have done wrong. Sorry not to respond before the patch was applied. Crazy week. > This is a patch for one of the ToDo items in languages/perl6/Todo. I have > updated the calling conventions

Re: [PATCH: P6C] update calling convention

At 3:20 PM -0500 5/5/04, Abhijit A. Mahabal wrote: This is a patch for one of the ToDo items in languages/perl6/Todo. I have updated the calling conventions in a bunch of places, but may have missed some. Applied, thanks. BTW, should I keep working on P6C? As A12 has just come out P6C may be heavil

[PATCH: P6C] update calling convention

Hi, this is my first patch ever (not just p6i: ever). So do tell me what I have done wrong. This is a patch for one of the ToDo items in languages/perl6/Todo. I have updated the calling conventions in a bunch of places, but may have missed some. One more subtest is failing because of my c

Re: More calling convention stuff

At 11:51 AM +0100 12/31/03, Leopold Toetsch wrote: Dan Sugalski <[EMAIL PROTECTED]> wrote: I've added a new op to the list, foldup, to make unprototyped calls (and some prototyped calls) a bit easier. The syntax is: foldup Px Now, as there is a second (almost duplicate) incarnation, the impl

Re: More calling convention stuff

Dan Sugalski <[EMAIL PROTECTED]> wrote: > I've added a new op to the list, foldup, to make unprototyped calls > (and some prototyped calls) a bit easier. The syntax is: >foldup Px Now, as there is a second (almost duplicate) incarnation, the implementation should really be an external subrout

More calling convention stuff

I've added a new op to the list, foldup, to make unprototyped calls (and some prototyped calls) a bit easier. The syntax is: foldup Px and Px gets a brand new Array PMC, with all the PMC arguments put into it. This includes all the args in PMC registers as well as args in the overflow array.

Re: IMCC - calling convention syntax

The optimizer could hoist the construct out of the loop... Assuming it can realize its possible to do that. Regards, -- Gregor On Tue, 2003-10-07 at 01:14, Leopold Toetsch wrote: > Will Coleda <[EMAIL PROTECTED]> wrote: > > As I realize my example is incorrect. =-) > > > Is there any reason no

Re: IMCC - calling convention syntax

Will Coleda <[EMAIL PROTECTED]> wrote: > As I realize my example is incorrect. =-) > Is there any reason not to make the ".pcc_call _parse" work also, > rather than having to construct a .Sub? We probably could construct a Sub PMC under the hood. The reason for 2 stages is efficiency though: If y

Re: IMCC - calling convention syntax

As I realize my example is incorrect. =-) Is there any reason not to make the ".pcc_call _parse" work also, rather than having to construct a .Sub? Regards. On Monday, October 6, 2003, at 09:19 PM, Will Coleda wrote: Currently, when calling a PCC Sub with the single Sub (and not with a Conti

IMCC - calling convention syntax

Currently, when calling a PCC Sub with the single Sub (and not with a Continuation) .pcc_begin prototyped .arg $S1 .pcc_call __parse somerandomlabel: .result $P1 .pcc_end Note the label... Every time I call a sub, I need to specify a new, unique label that I'm very unlikely to ever

calling convention and continuation ramblings

*num_reg_top; etc ... These are used when saving and restoring the registers. Are they used other than when following the (old) calling convention? I would like to get rid of these register stacks. In their place I would like to introduce a context object (call it a continuation?) that saves and restores

Re: Change to the calling convention, and other fallout from last week's perl 6 meeting

Dan Sugalski wrote: *) The vtable split needs to be defined and implemented. I'd like some macros to access the vtable entries themselves, since there may be a number of structural changes and I don't want to have to keep redoing the code every time some element shifts from one spot to anothe

Re: Change to the calling convention, and other fallout from last week's perl 6 meeting

At 1:09 PM -0500 2/14/03, [EMAIL PROTECTED] wrote: Dan -- *) There's going to be a bunch of named argument stuff that we should (though don't have to) put support in for. Perl 6 is going to make heavy use of them. I may be terminologically challenged here (if so, please forgive), but this s

Re: Change to the calling convention, and other fallout from last week's perl 6 meeting

s find metadata and there are names for the args, then it is possible to do by-name calling. I'm not clear, though, on what the Parrot representation of sub quux { print "baz= ", shift, "\n"; print "ni= ", shift, "\n"; } would be. It smell

Change to the calling convention, and other fallout from last week's perl 6 meeting

;t have to) put support in for. Perl 6 is going to make heavy use of them. *) One change to the calling convention--optionally passing in the name of the sub/method you're invoking. This is for autoloadish things where we may be making a call to foo, but really got GENERIC_FALLBACK_METHOD or

Convention

I hate to solicit, but I have a "favor" to ask someone who is willing. I would very much enjoy attending the O'reilly Open Source convention, particularly the Perl conference; however, I am less that wealthy (seeing as how I'm only 17). Would someone extremely generous