Ticket #1158 (new todo)

Opened 12 years ago

Last modified 11 years ago

t/op/01-parse_ops.t: figure out how to test parsing of pmc constant parameters

Reported by: particle Owned by:
Priority: normal Milestone:
Component: testing Version:
Severity: medium Keywords:
Cc: Language:
Patch status: Platform:


r13601 added a test to check parsing of every parrot opcode. but those that accept pmc constants are skipped, as i haven't figured out how to test them yet.

see t/op/01-parse_ops.t ~jerry

Change History

  Changed 12 years ago by coke

in reply to: ↑ description   Changed 11 years ago by jkeenan

  • component changed from none to testing

Replying to particle:

see t/op/01-parse_ops.t ~jerry

t/op/01-parse_ops.t no longer exists. Is t/compilers/opsc/01-parse.t its replacement.

I can't find '1158' in any relevant context in the source code.

Would any of these tests satisfy the request in this ticket?

t/pmc/pmc.t:198:pir_output_is( <<'CODE', <<'OUT', "Integer pmc constant " );
t/pmc/pmc.t:207:pir_output_is( <<'CODE', <<'OUT', "Float pmc constant " );
t/pmc/pmc.t:216:pir_output_is( <<'CODE', <<'OUT', "pmc constant" );
t/pmc/packfile.t:365:    # PMC constants
t/pmc/packfile.t:403:    is($I0, 2, "    and contains 2 pmc constants")

Thank you very much.


Note: See TracTickets for help on using tickets.