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

[BUG 5_61] Assertion failed: file "toke.c", line 216 #516

Closed
p5pRT opened this issue Sep 13, 1999 · 3 comments
Closed

[BUG 5_61] Assertion failed: file "toke.c", line 216 #516

p5pRT opened this issue Sep 13, 1999 · 3 comments

Comments

@p5pRT
Copy link

@p5pRT p5pRT commented Sep 13, 1999

Migrated from rt.perl.org#1363 (status was 'resolved')

Searchable as RT1363$

@p5pRT
Copy link
Author

@p5pRT p5pRT commented Sep 13, 1999

From @vanstyn

With 5_57 and 5_03, it instead prints​:

crypt% perl -we 'sub test { my $c = caller; *"${c}​::test"{SCALAR} }'
Scalar found where operator expected at -e line 1, at end of line
  (Missing operator before ?)
syntax error at -e line 1, near "*"${c}"
Bareword found where operator expected at -e line 1, near "${c}​::test"
  (Missing operator before :​:test?)
String found where operator expected at -e line 1, at end of line
  (Missing semicolon on previous line?)
Can't find string terminator '"' anywhere before EOF at -e line 1.
crypt%

Hugo

@p5pRT
Copy link
Author

@p5pRT p5pRT commented Sep 14, 1999

From @gsar

On Tue, 14 Sep 1999 04​:22​:07 BST, Hugo wrote​:

crypt% perl -we 'sub test { my $c = caller; *"${c}​::test"{SCALAR} }'
[...]
Assertion failed​: file "toke.c", line 216 at -e line 1.

Get change#4133 (posted here yesterday) for the fix.

Sarathy
gsar@​activestate.com

@p5pRT
Copy link
Author

@p5pRT p5pRT commented Sep 14, 1999

From @vanstyn

In <199909140721.AAA10152@​activestate.com>, Gurusamy Sarathy writes​:
:On Tue, 14 Sep 1999 04​:22​:07 BST, Hugo wrote​:
:>crypt% perl -we 'sub test { my $c = caller; *"${c}​::test"{SCALAR} }'
:[...]
:>Assertion failed​: file "toke.c", line 216 at -e line 1.
:
:Get change#4133 (posted here yesterday) for the fix.

Thanks, confirmed.

Hugo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant