RE: [PEAR-DEV] Re: [PEAR] Are you aware of SWIG?
| From: | Sam Liddicott | Date: | Mon, 20 May 2002 07:46:58 +0000 |
| Subject: | RE: [PEAR-DEV] Re: [PEAR] Are you aware of SWIG? | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-6224@lists.php.net to get a copy of this message | ||
> -----Original Message-----
> From: Martin Jansen [mailto:mail@martin-jansen.de]
> Sent: 20 May 2002 09:17
> To: Stig S. Bakken
> Cc: Jesus M. Castagnetto; Sam Liddicott; Matt Friedman; peardev
> Subject: Re: [PEAR-DEV] Re: [PEAR] Are you aware of SWIG?
>
> After reading some more details about Swig, I finally found out that
> applying coding standards indeed does not make much sense
> here. Instead
> we should put a big, fat warning at some prominent place for Swig
> generated modules that points out that the code is not CS conform for
> a good reason.
If some good wording could be suggested, and also generalised warning
against modifying the generated code I'll have it output in the generated
code.
Let's start with:
/*
* WARNING: This file was generated automatically. It may fail to
* conform your coding standards; and any changes you make may be
* lost if this file is regenerated.
*
* This file was originally generated as $ORIGINALFILENAME
* on $DATE $TIME
* by SWIG version $SWIGVERSION
* from these source files
* $OTHERFILENAME
* $OTHERFILENAME
* $OTHERFILENAME
...
*/
Any suggestions?
Sam