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
Inheriting from lexical classes seems borked #6251
Comments
From @lizmatShould this work? If not, why not? What would be the way to inherit from lexical classes in other compunits? ./A.pm6: ./B.pm6: $ PERL6LIB=. 6 'use B' |
From @zoffixznetTo the best of my knowledge: On Thu, 18 May 2017 03:52:42 -0700, elizabeth wrote:
No, because the symbol is lexical to the compunit. It's the same as how you won't be able
One way would be to export them: ./A.pm6: ./B.pm6: $ ./perl6 -I. -MB -e '' You can also use export sub: Or (I'm unsure what the end goal here is), take a special export arg and only export the class if it's present: ./A.pm6: ./B.pm6: $ ./perl6 -I. -MB -e '' Now change ./B.pm6 to: $ ./perl6 -I. -MB -e '' |
The RT System itself - Status changed from 'new' to 'open' |
From @LLFournFWIW theoretically you get at any 'my' symbol in another module through the On Fri, May 19, 2017 at 8:20 AM Zoffix Znet via RT <
|
From @jnthnOn Thu, 18 May 2017 15:19:26 -0700, cpan@zoffix.com wrote:
This and the rest of the response are correct; ticket rejected as there's no bug here. The point of lexical stuff in modules is that it's not visible outside unless explicitly exported. |
@jnthn - Status changed from 'open' to 'rejected' |
Migrated from rt.perl.org#131324 (status was 'rejected')
Searchable as RT131324$
The text was updated successfully, but these errors were encountered: