[rfk-dev] code status

[Tim Allen]

On 14 Oct 2005, at 19:37, Benjamin Molitor wrote:
> Would it be possible to maintain the NKI in messages.h and generate  
> the files from that during the make process? Because maintaining  
> two sets of NKI would probably not be the most elegat thing to do,  
> eiter.

How about an approach where the binary contains a minimal set of NKIs  
(if archives go back that far, perhaps 'the NKIs that came with the  
first version of RFK', a sort of RFK-classic) but the POSIX port will  
read external NKI sources as well - and have a policy that new NKIs  
will always go into external files.

This would have the following benefits:
  * Standalone RFK still works
  * Standalone RFK isn't huge
  * No worries about keeping the two message-lists is sync
  * If anyone complains that the internal list of NKIs is too short,  
there's an *artistic* reason why, rather than just 'the maintainer  
said so'.