Proposal: Add a second file extension that PilRC will recognize as a Palm resource file.
Background information: I use the VSS plugin with CodeWarrior. Because of this, I like to have all of my files (including headers) in the project file. This way I can quickly tell if a file is checked in or not even if it is not usually compiled. Beginning a few versions ago, pilrc (and the plugin) supported #include of other .rcp files. However, the file *must* have an extension of .rcp to be parsed as pilrc source. The problem is that if I add these sub rcp files to my project, the Pilrc plugin will try to compile them as well. I think the easiest solution is to modify the PilRC core library to parse a second extension as it does .rcp files now. This way I could add the sub files to my project and the plugin would not compile them directly, but files the plugin processes could #include them. I was thinking .rci; admittedly, .rip probably makes more sense, but I expect we'd have too many collisions on that one. It would almost seem logical that any unrecognized file is assumed to be a PilRC script, but PilRC is already coded with behavior for unrecognized file extensions -- it parses them as .h files. While this might not make sense, changing the default behavior would probably break at least some existing projects. Does anyone have any thoughts on this? And assuming it's a good change, how do I submit it? :) -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
