Frank Schönheit - Sun Microsystems Germany wrote:
Hi Rüdiger,
being late to the thread, and being the one who implicitly initiated
this ...
Why would you copy additional stuff into binfilter?
Because binfilter has a code base which lives several years in the past,
whilst the current code base moves forward constantly. At some point,
you simply can't stretch this any further.
My recent problem was some changes in basic (not basctl), which let the
build break in binfilter. There was no reasonable way (I could see) how
to adapt this in binfilter: I would have needed to back-port large parts
of SFX to BF_SFX (plus probably more), just to be able to use the new
basic API. That's certainly nothing I would do, as it bears a completely
unknown risk of breakage.
We once decided to freeze binfilter, IMO we cannot reasonably expect
that it will always be possible to adjust this stone-aged code to the
latest and greatest code which has undergone multiple years of
additional development.
Hi Frank,
Thanks for the details. Yes, I totally understand your problem, I think.
But, what you did is what I proposed, not what was written here as
recipe. You first evaluated to adapt binfilter to the incompatible
changes. After spotting all the difficulties you searched for an alternativ.
I could live with a rule to try adapting binfilter and, if that prooves
to be of unreasonable effort, take importing more code as an
(exceptional) alternative. But I am strictly against recommending a code
duplication as first choice.
Rüdiger
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]