>>> On 3/20/2008 at 1:03 PM, in message <[EMAIL PROTECTED]>, "Brad
Nicholes" <[EMAIL PROTECTED]> wrote:
>>>> On 3/20/2008 at 12:22 PM, in message <[EMAIL PROTECTED]>, Carlo
> Marcelo Arenas Belon <[EMAIL PROTECTED]> wrote:
>> On Thu, Mar 20, 2008 at 10:26:31AM -0600, Brad Nicholes wrote:
>>> 
>>> 1. Remove the "pymodule" configuration directive
>> 
>> +1
>> 
>>> 2. Add an optional type name to a module section to designate the interface 
>> type.  
>>>    module { } - #No designation, the default is C
>>>    module Python {} - #Python type module interfaced through mod_python
>>>    module Perl {} - #Perl type module interfaced through (what could be) 
>> mod_perl
>>>    etc....
>> 
>> I was thinking about doing an optional token instead :
>> 
>> module {
>>   lang = python
>>   ..
>> }
>> 
>> but whatever fits better with the confuse syntax parser will be ok.
>> 
> 
> I am already headed down that line of thinking.  After taking a little 
> closer look at libconfuse, my original proposal of an optional module type 
> won't work.  I had to switch to a language= directive just like you are 
> suggesting.  
> 
 
I just checked in the changes to remove the pymodule section directive and to 
introduce the language directive.  I am still working on the documentation for 
the directive change and how to write modules in C and python.

Brad


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers

Reply via email to