Hi Michael,
the wording "... was just not documented ...", "... documentation
problem ...", has been used so often now in this thread, that it just
moved up in my priority list (for this Example C Library theme) to the
lone very top position. So I'll not do an "exampleclib-1.1.0.spkg" or
so, before having dumped a decent amount of what I learned up to now
into the Wiki and the Sage Programming Guide.
It is tricky to write up things in such a way, that in order to create
a "pure C Library" spkg from scratch, one then only needs to copy-and-
paste the bits and pieces from the documentation. And from my
experience teaching students, a "Musterlösung" ("sample solution" in
english) is always very much appreciated.
As for the "Extlibs"-scripts infrastructure,
> There has been some discussion about doing something
> clever for optional and experimental spkgs, but nobody ever submitted
> any code for review. I am talking about sticking optional things into
> a per spkg tree so that removal would be trivial by nuking that tree
> only.
well, view it as prototypical code for "doing something for optional
and experimental" spkgs. I was not aware of discussions about this,
but I am relieved that I'm not the only one thinking in that
direction.
> Sage IMHO is not meant to be a hosting environment to
> develop library code outside the Sage library.
Sage might not be meant to be that, and probably this never will/
should be a goal for Sage. But I am already right now using Sage as
hosting environment, to develop library code "outside the Sage
library" (for the reasons I explained above). And I certainly came to
like it, and won't miss it again.
The "Open Source" nature of Sage certainly does encourage others to
use Sage in the ways they (think they) need it. It was this very "Open
Source" nature that made me "single out" the exampleclib project from
my own projects.
Cheers,
gsw
P.S.:
How to say "Seasons Greetings" in a political correct way in this
forum?
Well, have nice feast for those who have!
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
