$ make doc Failed to move 7.6:: Failed to move 7.4::
When trying to fix that, I get lost in the autodoc/xml code. Anyone?
Its in the traditional.xml, which have move nodes for those namespaces. Not sure if those just need to be removed, but doing that fixes the autodoc buils...
arne
On Sat, 15 Nov 2014, Stephen R. van den Berg wrote:
$ make doc Failed to move 7.6:: Failed to move 7.4::
When trying to fix that, I get lost in the autodoc/xml code. Anyone? -- Stephen.
Why do all these historical notes need to be removed from the docs? Some of them (regarding changes since 7.6) are still quite relevant today. Debian still comes with pike 7.6 and who knows, someone might want to port some of his code to run on pike > 8.0 and find those quite helpful..
Arne
On Sat, 15 Nov 2014, Stephen R. van den Berg wrote:
Arne Goedeke wrote:
Its in the traditional.xml, which have move nodes for those namespaces. Not sure if those just need to be removed, but doing that fixes the autodoc buils...
Yes, that's the spot I was looking for. Removing it is sufficient, fixed.
Stephen.
Arne Goedeke wrote:
Why do all these historical notes need to be removed from the docs? Some of them (regarding changes since 7.6) are still quite relevant today.
Quite, which is why they are still present in 8.0.
Debian still comes with pike 7.6 and who knows, someone might
Debian comes with 7.8, I'd say, not 7.6. Unless you use a different Debian than I do.
want to port some of his code to run on pike > 8.0 and find those quite helpful..
I reviewed the notes, and as you might notice, I kept the few which I deemed to be relevant in three years time (when 8.1 will likely follow up 8.0).
But, by all means, if you think I misjudged the relevance, roll them back in. Just keep in mind that this is against 8.1, not 8.0.
Stephen R. van den Berg wrote:
Arne Goedeke wrote:
want to port some of his code to run on pike > 8.0 and find those quite helpful..
I'd say, if you have code that ran under 7.6 or older, the most likely migration path would be to 8.0 where you can easily switch back to compat mode of 7.6 (or older). At which point you'll be doing your porting efforts and at which point you have full access to all the historical notes/clutter of the elder versions.
8.1 and onward drops compat support with 7.6 and older. Thus is an unlikely initial target when porting code to newer versions. The notes I deleted where mostly notes that *added* functionality. The only notes I kept where those that discussed incompatibilities. But still, I'd say someone which has code of <=7.6, will most likely port to 8.0 first.
I'm also concerned by some of your changes, e.g. to the XML parser and the string hashing algorithms.
I don't think anyone plans on running 7.4 _code_ in a few years time, but they may very well have _data_ that conform to rules introduced back when 7.4 was current. For instance, some of Roxen's customers have websites with hundreds of thousands of XML files in repositories where they could have markup errors that these relaxed parse rules were introduced to cope with, or there could be custom modules or databases where the 7.4 string hashing is used for checksums.
I'd appreciate if changes with potentially high impact are discussed here before being committed.
i believe that all information about compatibility changes should be kept for historical reasons. i find it always educational when i can see how a language (library, application, ...) evolved over time.
however anything not supported by a compatibility mode could be moved to a history section.
this is helpful not only for old code, but also for old documentation.
if i find some post explaining how to solve something in 7.4, then the history section can tell me how to fix that example to make it work in 8.0
the pike book for example just barely covers 7.6...
greetings, martin.
The information is actually still available, but in historical CHANGES file.
We do not offer those on the website, and most definitely not marked up in a nice way, however.
We might want to do that.
Stephen R. van den Berg wrote:
Arne Goedeke wrote:
Its in the traditional.xml, which have move nodes for those namespaces. Not sure if those just need to be removed, but doing that fixes the autodoc buils...
Yes, that's the spot I was looking for. Removing it is sufficient, fixed.
Well, doing "make doc" in 8.1 now results in: Failed to move 8.0::
Any ideas?
pike-devel@lists.lysator.liu.se
-
Arne Goedeke -
Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum -
Jonas Walld�n ＠ Pike developers forum
-
Martin Bähr -
Per Hedbor () ＠ Pike (-) developers forum
-
Stephen R. van den Berg