Re: [Axiom-developer] hyperdoc source links are often wrong

[Bill Page]

William and Tim,

The problem to which William is referring is caused by
the way Tim has re-organized the original *.spad source
files into *.spad.pamphlet files. The mapping is many-to-
one where there used to be 1000+ *.spad files there are
now only 300+ *.spad.pamphlet files. The new OpenSource
makefile extracts the individual *.spad files as intermediate
files as needed by the rest of the build, but these are not
the ones passed on to the 'mnt' release directory. Instead
the current makefile extracts the merged *.spad.pamphlet
files and calls them *.spad files in the 'mnt' directory,
but these correspond to the 300+ *.spad.pamphlet files
not the 1000+ original *.spad files. I agree that the fact
that these appear with the suffix ".spad" is confusing because
the names because these are not the original *.spad
files.

I think one reason that Tim may have done that was to keep
these source files in sync with the corresponding *.dvi
documentation files - that is a good thing. But unfortunately
it breaks Axiom's original method of referring to the
appropriate source.

Perhaps the *.spad files extracted as intermediate files
could just be copied into the 'mnt' directory instead of
the re-packaged versions. That would at least make Axim
work the way it used to. But in the new system of
code+documentation in pamphlet files really one is not
supposed to be editing the *.spad files directly, rather it
is the pamphlet file that is should to be changed - both
code and associated documentation.

So I suppose really Axiom should be supplying the new
*.spad.pamphlet file names. This might be a little difficult
since currently Axiom itself does not understand the
mapping of spad to pamphlet files. I think that something
would have to be changed in the Axiom database files.

Regards,
Bill Page.

William Sit wrote:

>Tim:
>
>The hyperdoc and )show commands associate the source file of a package with
>abbreviation xxx to xxx.spad.  This is not correct and sometimes the xxx is not
>even close to the correct file name. Please note that one spad file may contain
>many domains and packages. So most clicks in hyperdoc on the source file 
>results
>in file not found and it is a guessing game what the right file is.
>
>An example is SOLVETRA package where the spad file is
>transsolve.spad; another is EF where the file is elemntry.spad.
>The NAG version is correct, so something in the OpenSource version is
>responsible for the change.
>
>Thanks for the April release.
>
>William
>
>
>_______________________________________________
>Axiom-developer mailing list
>address@hidden
>http://lists.nongnu.org/mailman/listinfo/axiom-developer
>
>  
>