Changes between Initial Version and Version 5 of Ticket #1868

Show
Ignore:
Timestamp:
01/13/11 20:51:33 (4 years ago)
Author:
plobsing
Comment:

converted from RFC to deprecation

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1868

    • Property type changed from RFC to deprecation
    • Property summary changed from RFC: deprecate PIR to [DEPRECATED] PIR compiler availability
  • Ticket #1868 – description

    initial v5  
    11PIR as a language is currently always available in parrot. This privileged status is part of why PIR is a growing pain for Parrot (usually experienced as hatred for IMCC). 
    22 
    3 PIR should be no different to parrot than any language. Therefore, it should not be baked-in to libparrot and be always available. In stead, PIR should become a separately loadable component. To get the PIR compiler, a load_language "PIR" instruction should be issued first. 
     3PIR will become no different to parrot than any language. It will not be baked-in to libparrot and be always available. In stead, PIR will become a separately loadable component. 
     4 
     5PIR will remain available to Parrot programs, however it will require loading before use (via the load_language instruction). 
     6 
     7A separate executable (tentatively named "parrot-imcc") will be made available for compiling and running PIR programs as the main parrot executable does today.