Re: [Gretl-devel] remaining feature to-do list

> Again: I won't go into details on this, but one of the things we plan to > do this week is to start working on a complete Backus-Naur > representation of hansl (that we don't have at the moment). Apart from > making it possible to re-implement a number of things more efficiently, > it should give us a much clearer idea on how to modify hansl for 2.0: > what to add, what to deprecate, what to modify, etcetera. Once you have > hansl in Backus-Naur form what you're suggesting should be feasible. > Had never heard of that BN form, briefly looked it up, indeed seems to make extensions easier to handle... interesting. I have no idea how time-consuming this internal change is; of course it would be nice if gretl 2.0 could have it, but OTOH that could also be a reason for a 3.0.