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

Implement all TODO comments in t/pmc/parrotio.t #535

Open
leto opened this issue Nov 5, 2009 · 2 comments
Open

Implement all TODO comments in t/pmc/parrotio.t #535

leto opened this issue Nov 5, 2009 · 2 comments

Comments

@leto
Copy link
Member

leto commented Nov 5, 2009

There are many things like:

$P1 = # TODO create a callback here

in the code. Write proper tests for these TODO comments.

If you close this ticket, coke++ will buy you beer.

Originally http://trac.parrot.org/parrot/ticket/1204

@jkeenan
Copy link
Contributor

jkeenan commented Feb 25, 2011

Many? I only see these 4 (as of now):

[parrot] 507 $ grep -in TODO t/pmc/parrotio.t
35:pir_output_is( <<'CODE', <<'OUT',
  'open and close - synchronous',
  todo => 'not yet implemented' );
117:    <<'CODE', <<'OUT', 'print, read, and readline - synchronous',
  todo => 'not yet implemented' );
170:# TT #1204 pir_output_is( <<'CODE', <<'OUT',
  'print, read, and readline - asynchronous',
  todo => 'not yet implemented' );
173:pir_output_is( <<'CODE', <<'OUT', 'buffer_type',
  todo => 'not yet implemented' );

Anyone want to take a stab at this?

Thank you very much.

kid51

@jkeenan
Copy link
Contributor

jkeenan commented Feb 25, 2011

Replying to jkeenan:

Many? I only see these 4 (as of now):

On closer look, I see that while there are only 4 tests that are TODOed, there are many items in inline comments that don't match m/todo/i but do indicate things that need to be done.

See, inter alia, TT #1177 and TT #1178.

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

No branches or pull requests

2 participants