[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: What about az_python.m4?
From: |
Guido Draheim |
Subject: |
Re: What about az_python.m4? |
Date: |
Mon, 17 Jan 2005 00:34:34 +0100 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040906 |
Peter Simons wrote:
> The macro legacy/installed_packages/az_python.m4 has
> appeared in the CVS repository, but it doesn't contain any
> markup at all, as far as I can tell. Is that supposed to be
> that way for some reason?
>
Ouch, I was looking over it and it did look good but actually
those comment block up front is written with "#" marks instead
of the expected "dnl" marks. Essentially leaving it empty after
being rendered to html.
I did want that macro set to be out as soon as possible so
that Robert has a good background for promoting the usage
and extension of the macro set. You're right, the special
marks of the ac-archive submission format are missing. We'll
fix that real soon.
-- cheers, guido
Guido Draheim wrote:
> Robert White wrote:
>
>>> Hi, Guido.
>>>
>>> Enclosed are some macros to help embed Python in an application. They
>>> worked in MacOSX, gentoo Linux and Cygwin which are the environments
>>> that I have at home. I prefixed them with AZ_ for testing purpose so
>>> that they would not interfere with anyother macros till I got them
>>> debugged.
>>>
>>> Please feel free to use them in any manner that you see fit.
>>>
>>> If you would like me to maintain them, that would be ok with me. If
>>> not, that is fine too. I made them to see if I could get application
>>> authors to use them so that their programs would support MacOSX. So, I
>>> will be contacting most authors who embed Python in their apps to try
>>> and use them.
>>>
>>> My small contribution to open source.
>>>
>
>
> Exceptional quality. Just one hint: it would be best to add
> additional arguments ACTION-IF-TRUE, ACTION-IF-FALSE to all
> the macros (or atleast IF-FALSE) - that is common practice
> with other ac macros and it ensure that later macro users do
> not play tricks with the internal variables when they want
> to expand the behavior on what they have already.
>
> -- cheers, guido
>