Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

output from .perl for regex #593

Closed
p6rt opened this issue Jan 8, 2009 · 9 comments
Closed

output from .perl for regex #593

p6rt opened this issue Jan 8, 2009 · 9 comments
Labels

Comments

@p6rt
Copy link

p6rt commented Jan 8, 2009

Migrated from rt.perl.org#62068 (status was 'rejected')

Searchable as RT62068$

@p6rt
Copy link
Author

p6rt commented Jan 8, 2009

From @finanalyst

The output from .perl for a regex could be more useful than currently.
I have
$ perl6

my $x = /<digit>+/; say $x.perl
{ ... }

Doesnt seem to matter what the regex is.

Perhaps,

Regex { <digit>+ }

@p6rt
Copy link
Author

p6rt commented Jan 10, 2009

From @masak

Richard (>)​:

The output from .perl for a regex could be more useful than currently.

[...]

Perhaps,

Regex { <digit>+ }

That does not seem to be legal Perl 6 to me. The idea of .perl is to
output runnable code, after all. How about this instead?

/ <digit>+ /

@p6rt
Copy link
Author

p6rt commented Jan 10, 2009

The RT System itself - Status changed from 'new' to 'open'

@p6rt
Copy link
Author

p6rt commented Jan 10, 2009

From @finanalyst

/ <digit>+ / is what I thought it should be.

{ ... } is what rakudo current gives, which from the point of view of
runnable code and comprehensible output, are wrong.

Carl Mäsak via RT wrote​:

Richard (>)​:

The output from .perl for a regex could be more useful than currently.

[...]

Perhaps,

Regex { <digit>+ }

That does not seem to be legal Perl 6 to me. The idea of .perl is to
output runnable code, after all. How about this instead?

/ <digit>+ /

@p6rt
Copy link
Author

p6rt commented Jan 11, 2009

From @pmichaud

On Sat Jan 10 10​:00​:20 2009, richardh wrote​:

/ <digit>+ / is what I thought it should be.

{ ... } is what rakudo current gives, which from the point of view of
runnable code and comprehensible output, are wrong.

In general, being able to use .perl on subs and methods implies that an
implementation must either (1) be able to construct a Perl 6
representation of the compiled version of the sub/method, or (2) attach
to each sub/method a text copy of the source used to create it.

I'm not sure how practical either of these are going to be, so would
like some clarification or confirmation from p6l first. In the
meantime, I'm marking this ticket as stalled for now.

Thanks!

Pm

@p6rt
Copy link
Author

p6rt commented Jan 11, 2009

@pmichaud - Status changed from 'open' to 'stalled'

@p6rt
Copy link
Author

p6rt commented Mar 3, 2013

From @coke

Marking as "rejected" ; this belongs in the spec queue, not the rakudo queue.

Opened a ticket as Raku/old-design-docs#30, with a link back to this ticket.

Thanks for the report, hopefully we can get an answer from @​Larry.

On Sun Jan 11 07​:06​:08 2009, pmichaud wrote​:

On Sat Jan 10 10​:00​:20 2009, richardh wrote​:

/ <digit>+ / is what I thought it should be.

{ ... } is what rakudo current gives, which from the point of view of
runnable code and comprehensible output, are wrong.

In general, being able to use .perl on subs and methods implies that an
implementation must either (1) be able to construct a Perl 6
representation of the compiled version of the sub/method, or (2) attach
to each sub/method a text copy of the source used to create it.

I'm not sure how practical either of these are going to be, so would
like some clarification or confirmation from p6l first. In the
meantime, I'm marking this ticket as stalled for now.

Thanks!

Pm

--
Will "Coke" Coleda

@p6rt
Copy link
Author

p6rt commented Mar 3, 2013

The RT System itself - Status changed from 'stalled' to 'open'

@p6rt
Copy link
Author

p6rt commented Mar 3, 2013

@coke - Status changed from 'open' to 'rejected'

@p6rt p6rt closed this as completed Mar 3, 2013
@p6rt p6rt added the spec label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant