Ticket #511 (closed cage: done)

Opened 6 years ago

Last modified 5 years ago

[CAGE] deprecate searching runtime/parrot for libraries and includes

Reported by: allison Owned by:
Priority: normal Milestone:
Component: library Version:
Severity: medium Keywords:
Cc: Language:
Patch status: Platform:

Description

Currently, the library and include searches hit runtime/parrot in addition to runtime/parrot/library or runtime/parrot/include. This behavior is deprecated and will be removed after 1.4.

This means that all calls to:

load_bytecode 'library/foo.pbc'
.include 'include/bar.pir'

Will need to be changed to a simple:

load_bytecode 'foo.pbc'
.include 'bar.pir'

And the following is just plain evil and never should have been done in the first place:

.include 'library/dumper.pir'

Move dumper.pir to runtime/parrot/include, or split it into the "library" portions and the "include" portions.

Change History

Changed 5 years ago by NotFound

All 'library/' are removed, except from examples/sdl that AFAIK are not working.

I replaced the include of dumper.pir with load_bytecode dumper.pbc, looks like there was no real reason to use the include.

But I have a doubt about this file:

$ ./parrot runtime/parrot/library/dumper.pbc
# usage:
.sub main
    load_bytecode 'Data/Dumper.pbc'

    .local pmc foo, dumper
    foo    = new 'ResizablePMCArray'
    dumper = new 'Data::Dumper'

    dumper.'dumper'( foo, 'foo' )
.end

Does this means that this file is obsolete and Data/Dumper must be used instead?

Changed 5 years ago by NotFound

Dropped all include/ I've found in r38718

Changed 5 years ago by NotFound

The last .include 'library/....' has been fixed in r39338. With the exception, again, of sdl examples.

Changed 5 years ago by allison

  • status changed from new to closed
  • resolution set to done

I removed 'runtime/parrot' from the library and include search paths in r40442, allowing plenty of time for testing before 2.0. Resolving this ticket, but leaving it linked in DEPRECATED.pod for now (can be removed after testing).

Note: See TracTickets for help on using tickets.