# New Ticket Created by Will Coleda # Please include the string: [perl #48497] # in the subject line of all future correspondence about this issue. # <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=48497 >
When building parrot, we get the following warning: setstdout_p SKIPPED: not in ops.num nor ops.skip setstderr_p SKIPPED: not in ops.num nor ops.skip This should instead be an error and stop the build. If an opcode is in one of the primary ops files, it should be built with parrot; If it's experimental and we don't want it to be kept in ops.num forever, then it should be in experimental.ops.. Making this an error insures that whoever adds an opcode knows they need to add it to experimental.ops or to ops.num; These ops seem to have been committed in r13773 over a year ago and have apparently never been used. (for bonus points, once you make this an error, move these two ops into experimental.ops, since we don't know what their final disposition is.) -- Will "Coke" Coleda
