Hello list.
i wrote:
|Yes it is true that we should ship something out, finally.
|I therefore changed my plans and will ship out a v14.9.0 which
|does not include the three major features that i am looking
|forward to, which i want to see happen before i turn to the other
|two projects i want to maintain. It still will bring a large
|number of improvements and new features.
So i want to delay this a little bit longer once more. We have
made some progress that i never even dreamed of, e.g. v14.9.0 will
be able to do
? define __xv {
# Be careful to choose sh(1)ell-style on _entire_ line!
# Result status ends up in $!
localopts 1;wysh set verbose;ignerr eval "${@}";return ${?}
}
? ghost xv '\call __xv'
? xv help set
We have macros with arguments, we have `eval', and we can sequence
command lines as above if a bit of care is taken. That is, it
could even be expected that people, and that of course also
including you reading this already now, start doing _something
more sophisticated_ with it, because it slowly becomes possible.
And then they should be able and not run into a dead-end with high
walls everywhere. I mean, message access still sucks completely,
anyway.
But what ships out should be as much as possible upward
compatible, so that we get over the backward incompatibilities
once, i.e., before people start really using it for the more
sophisticated things. That is to say, i think it is _very_ likely
that even you don't run in backward incompatibilities for your use
case, but you might if i don't take some more time now in the
future. That is worth it.
So i hope to be able to get out a release candidate some weeks in
the future, and i really hope for a release at the end of March.
Thank you. And
Ciao.
--steffen
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
__________________________________
[email protected]
