On 11/28/05, Chip Salzenberg <[EMAIL PROTECTED]> wrote: > Oh, one other thing for the renaming game: > > IMC vs. PIR > Two names enter > One name leaves > > /me giggles
this is now referenced in DEPRECATED (thanks to will,) and the remaining .imc files in the parrot tree are quickly being converted to .pir files. this should be done by the time parrot is released (this weekend?) note that this includes runtime libraries like Data/Dumper.imc, JSON.imc, etc. you may need to modify your code to point to the renamed libraries. for those with a large base of .imc files, don't dispair. parrot will continue to recognize the .imc extension for the time being. as a courtesy to existing users who need to convert existing files to the new extension, the .imc file extension will continue to be supported in the coming release. but soon enough, if there are no objections, it'll be ripped out, so be prepared. two simple rules to use the proper file extension: ~ writing PIR? name your file foo.pir, or convert an existing one from foo.imc ~ writing PASM? name your file foo.pasm ~jerry
