Jani Taskinen wrote:
Krhm...you should make it to produce code that meets
our coding standards.. :)
Use tabs, ...
sure, but especially tabs have a very low priority on my list,
as having them as '\t' in the generating PHP code hurt readability
a lot (and emacs is not clever enoug
Krhm...you should make it to produce code that meets
our coding standards.. :)
Use tabs,
if (foo) {
...
}
etc.
--Jani
On Wed, 26 Feb 2003, Hartmut Holzgraefe wrote:
>l0t3k wrote:
>> Hartmut,
>> will this also generate zend_parse_param
l0t3k wrote:
Hartmut,
will this also generate zend_parse_parameters calls based on prototype ?
Sure, see the two samples below. It even adds return statements for the
return type specified in the proto where possible.
But unlike the current ext_skel it also supports code generation for
php.ini va
The current one does, so it better...
On Wed, 19 Feb 2003, l0t3k wrote:
> Hartmut,
> will this also generate zend_parse_parameters calls based on prototype ?
>
> l0t3k
> "Hartmut Holzgraefe" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> >
> > i've just added the first working
Hartmut,
will this also generate zend_parse_parameters calls based on prototype ?
l0t3k
"Hartmut Holzgraefe" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> i've just added the first working results of a replacement for the good
> old ext_skel script in php/scripts/ext_skel_ng
