Re: [AD] Documentation system 2009 |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: Coordination of admins/developers of the game programming library Allegro <alleg-developers@xxxxxxxxxx>
- Subject: Re: [AD] Documentation system 2009
- From: Evert Glebbeek <eglebbk@xxxxxxxxxx>
- Date: Sat, 10 Jan 2009 17:07:23 +0100
On 10-Jan-09, at 10:03 AM, Peter Wang wrote:
Patch attached. The scripts are written in shell (they'd be trivial
to
rewrite, even in C). Natural Docs have been extracted but not
reformatted.
The CMake build will generate HTML, man and info documents (if
enabled).
I'll get some more opinions before committing.
Seems fine to me!
As to what language they should be written in: he important things is
that it works and is maintainable. Shellscripts are easy to use to set
things up but become annoying to maintain (in my experience).
I know Python and I hate it with a passion (unfortunately I have no
choice but to use it for some work related projects). I know and love
Perl and if properly written, you'd hardly know it wasn't C (I've
copy&pasted code between C and Perl on a few occasions, only
difference was having to stick $ in front of a variable name in Perl).
So I think it's clear there's not going to be any one solution that
everyone would be happy with, ruling out both. This is even before we
address Windows.
So I like the suggestion of using C (or C++) to do this. I would also
have a slight preference for C over C++, but whoever codes it up gets
to decide, I guess.
Evert