Ralf Hemmecke wrote:
>
> On 11/08/2015 08:42 PM, Waldek Hebisch wrote:
> > Doing similar thing without arguments is much harder
>
> Certainly true, but, that's more or less what I have done here for
> fricas.github.io. Search for example "if" on
> http://fricas.github.io/api/Matrix.html . I guess, that I probably have
> not caught and simplified every case, but the list of functions exported
> from a domain together with the respective conditions are there. I even
> believe I did it somewhat better than what Hyperdoc does for unspecified
> parameters of a domain, because I at least take the type of the
> parameter into account and use that to reduced conditional exports.
>
> > So, it would be nice feature, but actually needs substantial
> > effort to implement.
>
> I believe that I have already done the "substantial" part.
>
> https://github.com/hemmecke/fricas/blob/master-hemmecke/src/doc/api.spad
>
> That code generates .rst files for *all* constructors. Maybe that would
> even be enough for Johannes. Perhaps it would be a bit faster, if only
> the page for the constructor in question is generated. I think that
> would need a bit of adaptation, because (I believe) I didn't had this
> use case for a single constructor not in mind when I created it.
>
> Unfortunately, I'll not be able to do much in this direction in the next
> few weeks, but Johannes, if you ping often enough, I might start working
> on it some day.
>
> Anyway, api.spad does not use the add part, it just looks at the
> category part, so it only lists what should be there. The user would
> have to single out what is already in the file.
Well, finding what is implemented is the hard part.
> Since hyperdoc actually does the same, if (after compilation) one looks
> at the hyperdoc page for the new constructor, there will be not much
> difference to api.spad.
Have you tried what I wrote: given paremeters to constructor
HyperDoc can find what is implemented and where.
>
> In fact, thinking about this... Waldek, since after compilation the
> signature list will be on a hyperdoc page, why cannot a postprocessor
> list the differences between all necessary and all actually implemented
> function signatures? That actually sounds like there is no "substantial
> effort", just an effort to put the pieces together.
Many functions are inherited. In principle we could look at
non-inherited signatures and find out which are not implemented.
But ATM compiler just keeps list of signatures, without distinction
if they are inherited or not. And it is typical that most signatures
are inherited.
--
Waldek Hebisch
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/fricas-devel.
For more options, visit https://groups.google.com/d/optout.
