|
== Language and library organization ==
(Moved to [[Rosetta Code:Village Pump/Semantic MediaWiki/Semantics]] (--[[User:Short Circuit|Michael Mol]] 18:05, 29 August 2010 (UTC)))
== Yorick ==
I really appreciate all the work you're doing with language, implementation and library association and documentation. I've got some ideas about associating those pages within the context of Semantic MediaWiki. Would you be interested in hashing this out and helping get it implemented? (It should only involve making changes to wiki pages, much like what you're already doing.)
Your language list included "Yoric", but the language's actual name is "Yorick". I corrected it in your listing so that I could correct the relevant categories. -- [[User:Sekoia|Sekoia]] 22:38, 10 October 2010 (UTC)
My thoughts are:
* Distinguish between library, API and bindings between libraries and bindings to a language. That way:
** An example said to use, e.g. PyGTK could be programattically assumed to use GTK, and an example said to use Xcb could be assumed to use X11.
** An example using GLib could be assumed to be using OpenGL
** GLUT is both an API and a library, but the original has long lapsed. There are replacements, though, and they could all be assumed to be implementations of GLUT.
** The ISO89 C Runtime has an API spec, and any library/C language binding that correctly implements it could be reasoned by SMW to provide that runtime, and so any C example that uses an API spec could be reasoned to be an example use of those libraries.
== Clipper / Harbour / XBase ==
That's the gist of the idea, for now. Does this strike your interest? --[[User:Short Circuit|Michael Mol]] 17:28, 13 August 2010 (UTC)
Do you have any objection to Clipper and Harbour being stored under an XBase heading in task solutions? It would seem to me better than duplicating code under separate Clipper and Harbour headings. [[User:Axtens|Axtens]] ([[User talk:Axtens|talk]]) 13:00, 8 June 2014 (UTC)
|