On Wed, Oct 26, 2016 at 02:21:57PM +0200, Dominik Vogt wrote: > First of all I hope I'll be able to find the crash caused by a free of a > string that is still > used, then experiment with it to see whether a step by step replacement of > the old > parser is feasible while keeping the old parser around for a while. > Disentangling the > builtin functions from the parser without changing their syntax is an > important step towards a new parser with a new syntax. As long as all the > functions do their own parsing, replacing the syntax is a huge amount of > work.
Yes, I remember that bug when we first started this, but it was a pain to track down. Hopefully you'll have more luck. :) But what you're describing is the biggest piece of work which would almost define fvwm3. Thus far, there's still an on-going discussion about how we're going to do that. Heck, we haven't even declared fvwm2-stable or fvwm-2.6.7 yet. Aren't you jumping the gun a little? I'd argue---quite strongly---that any work towards a new parser should be done with breaking everything completely. Sure, you can still keep some of the surrounding things, but trying to maintain backwards-compatibility isn't necessary given the measures we're putting in place for fvwm2's future. But at the moment, we haven't even discussed what that will look like, or what requirements we might have. I started to do that recently when I put out a proposal for a new syntax to see how that fared. Oh, and the point of a separate repo still stands, in my eyes. You might think it moot, or even an unnecessary point, but I feel it's a very important one. It reinforces (psychologically) that it's separate from fvwm2. It reinforces that fvwm3 is discrete, and it reinforces the idea that it will become divergent from fvwm2 quite quickly. It's not as if we're backporting features or fixes between the two. Copy---if it makes you feel any easier---the entirety of the files from fvwm's master branch to new fvwm3 repository. Do your work there, the set up is easy. Having a separate fvwm3 repository also allows to integrate anything we wish to the main fvwm website as well (when that becomes appropriate). Kindly, Thomas
