Not necessarily, but that's where I'm starting, it is is going to be similar to the mozilla developer network. A friendly, wiki-based method of education about those languages and tools with example source, example output, best practices, use cases, etc. Whereas the existing documentation serves a purpose a lot closer to reading the Specifications of the C language than "teaching it". Only serving to be helpful to seasoned developers, making the C Language (and other GCC Languages) a lot scarier/overwhelming to learn. Microsoft sort of provides this for the C language with their MSDN C documentation, and this is obviously going to be in direct competition with that (IMHO showing that community-powered open source wiki documentation prevails over their proprietary/closed alternative.)
Also, the extension is very small in terms of hard drive usage, and resource usage, and will have nearly no effect on Libreplanet. It will just take a minute or two for a sysadmin to paste it into the extensions folder and *boom*. On Mon, Oct 28, 2013 at 3:24 PM, Rudolf <[email protected]> wrote: > In the worst case scenario you can link to some free service that provides > pastebin with syntax highlighting. > > Are you basically porting the texinfo docs for libc to wiki format? > On Oct 28, 2013 5:32 PM, "David Gumberg" <[email protected]> wrote: > >> I'm currently trying to get a project called "GNU Developer Network" >> going, which will provided online wiki-based documentation for GNU >> Development tools, and development for GNU systems. This includes >> documenting GCC and the GNU libc. The first task is to document all the >> functions in GNU libc, with examples, best practices, etc. To do this, I >> need a fast, clean, and concise way to write code examples. It would be of >> great help if you could install the code ( >> https://www.mediawiki.org/wiki/Extension:Code) for mediawiki. So I could >> just do "<source lang="c"></source>". This would be really great! Thanks! >> (sent this to both libreplanet-dev and libreplanet-discuss since I wasn't >> sure where this should go) >> >> ~David >> >
