load_bytecode semantic differs between .pir and .pbc loading

[NotFound]

This example shows the problem:

# foo.pir

.sub foo
  say 'foo'
.end

# bar.pir

.HLL 'bar'

.sub main :main
    load_bytecode 'foo.pbc'
    foo()
.end

$ parrot bar.pir
foo
$ parrot -o foo.pbc foo.pir
$ parrot bar.pir
Could not find sub foo
current instr.: 'main' pc 7 (bar.pir:7)

When loading the pir, either by explicitly asking or, as in this example, because the pbc doesn't exist, the semantic changes: the subs are inserted in the current HLL if there is no HLL directive in the loaded file.

See TT #1692

[NotFound]

See also TT #1686

[plobsing]

Replying to NotFound:

When loading the pir, either by explicitly asking or, as in this example, because the pbc doesn't exist, the semantic changes: the subs are inserted in the current HLL if there is no HLL directive in the loaded file.

I've attached a small patch that puts the start of every PIR file compilation into the default HLL. I'm not sure if this is the correct behaviour (it does pass fulltest), but at the very least it is consistent.

[NotFound]

Now that the dynop loading problems should be solved is time to attack this issue. Slightly modified version of the patch applied in r48578. Let's see what happens.

[NotFound]

Nothing bad happened, closing ticket.