On Oct 22, 2005, at 21:02, Bernhard Schmalhofer via RT wrote:
Using registers for passing command line options to a specific runcore
seem hazardous to me. Especially as a 'char *' is put where a 'STRING
*'
is expected.
Yep. This has always been a hack to pass the outfile along.
As Parrot_setup_args() is so far only used for passing 'output' to the
exec runcore, I propose a quick fix.
i. Do not use STRING register for passing options
ii. Move interp->imc_info->output to interp->output_file and use
interp->output_file for all uses of the 'output' option.
or use interp->current_file (or rename that) - this is already marked
during DOD and otherwise unused. A global current_file doesn't make any
sense. The info is also covered by the debug PBC segment.
CU, Bernhard
leo
