Jonathan Scott Duff <[EMAIL PROTECTED]> wrote:
> Is there some reason that runtime/parrot/library isn't in the list of
> search paths for both include_paths and dynext_paths?
No. We have:
load_bytecode => Parrot_load_bytecode
*.pbc => PackFile_append.pbc => Parrot_readbc =>
Parrot_locate_runtime_file( ... PARROT_RUNTIME_FT_PBC)
else => IMCC_compile_file => imcc_compile_file =>
Parrot_locate_runtime_file( ... PARROT_RUNTIME_FT_SOURCE)
In Parrot_locate_runtime_file() there is no special case for these file
types, they go along with the include paths, which isn't quite right.
Therefore we'd need another default search path for these two file
kinds.
Takers wanted.
> -Scott
leo
