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. |
| 3 | PIR 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 | |
| 5 | PIR will remain available to Parrot programs, however it will require loading before use (via the load_language instruction). |
| 6 | |
| 7 | A separate executable (tentatively named "parrot-imcc") will be made available for compiling and running PIR programs as the main parrot executable does today. |