Return-Path: Delivered-To: apmail-httpd-apreq-dev-archive@httpd.apache.org Received: (qmail 76808 invoked by uid 500); 15 Jul 2003 17:08:32 -0000 Mailing-List: contact apreq-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list apreq-dev@httpd.apache.org Received: (qmail 76797 invoked from network); 15 Jul 2003 17:08:32 -0000 Received: from erato.logilune.com (HELO mail.logilune.com) (195.154.174.52) by daedalus.apache.org with SMTP; 15 Jul 2003 17:08:32 -0000 Received: from stason.org (localhost.logilune.com [127.0.0.1]) by mail.logilune.com (Postfix) with ESMTP id CFE7278E9B; Tue, 15 Jul 2003 19:08:34 +0200 (CEST) Message-ID: <3F1431C5.5050606@stason.org> Date: Tue, 15 Jul 2003 19:54:29 +0300 From: Stas Bekman Organization: Hope, Humanized User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030428 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Joe Schaefer Cc: apreq-dev@httpd.apache.org Subject: Re: libapreq-2 doxy docs References: <3F142774.8090108@stason.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Joe Schaefer wrote: > Stas Bekman writes: > > >>Joe Schaefer wrote: > > > [...] > > >>But why do you need this automatic handling at all? What's wrong with >>writing POD in first place? The C and Perl apis have little overlap if >>at all, no? > > > Right. The issue really has nothing to do with XSBuilder's doc generation, > since we don't use that at all. What I'm wondering is whether or not we > should be using XSBuilder::ParseSource to parse the header files, when it > appears that doxygen does a far better job (for instance, doxygen > can preprocess and expand selected macros, whereas ParseSource, being P::RD > based, cannot). > > Of course, with the workarounds in build/xsbuilder.pl, we are able > to use XSBuilder::ParseSource successully right now, so I'm not going > to try and "fix" what isn't broken. However, if something does break in > the future, or we really want to eliminate build/xsbuilder.pl from the > build system, then I suggest we look at doxgen's perlmods as a clean > replacement for XSBuilder::ParseSource. My mind is jetlagged, are you saying that you are considering to use doxygen to generate the XS glue code? __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:stas@stason.org http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com