Hi Randall and James,
Looking at the MacPorts API, I just don't see where the port API
comes into play. I guess I'm just confused.
I don't blame you for being confused. I'm confused every time I
look at that code. It's a ball of worms. The more I know about it
the more I want to rewrite it ;) But time, alas, intervenes.
That makes me feel a lot better; I thought I was just too dim-witted
to understand it. Perhaps, as a first step towards rewriting the
source, those who understand some of it can start documenting it? No
need to do it all at once; one function at a time would do,
explaining what it's supposed to do, how it goes about it and where
it fits in the scheme of things. That way it'll make it more likely
that someone will turn up with time to attempt a rewrite without
being intimidated out of the idea. Anders has put a port of tcldoc
into the tree, so that should be a useful format to start with.
Kind regards,
Maun Suang
--
Boey Maun Suang (Boey is my surname)
Email: boeyms at macports dot org
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev
