A runtime option would be fine with me.
Am 08.10.2014 um 20:08 schrieb Peter Bex:
On Wed, Oct 08, 2014 at 08:04:17PM +0200, "Jörg F. Wittenberger" wrote:
In this particular case I will be forced to decide my priorities: I'm
sitting on some improvements and threading fixes and cleanups I've been
talking about on once about a time. Currently I'm busy documenting
other things. That's why you did not see patches yet. But I'd really
love to feed them back into mainline chicken.
Breaking out the scheduler might be helpful with this. But changing the
meaning of strings would force me to change a huge amount of dependent
source to even be able to merge my changes back. That would easily
delay these things further.
Could we refine this "forbid NUL in strings" weaken to "deprecating NUL
in strings" until the next major version please.
Thanks for speaking up, I hadn't considered how big of a problem this
would be for large, existing projects. We could possibly make it a
runtime option, so the checking (or just the enforcing) could be enabled
or disabled at will.
Cheers,
Peter
_______________________________________________
Chicken-hackers mailing list
Chicken-hackers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-hackers
