At 19:49 05/04/2003, Philip Olson wrote:
> Again: This point of view seems to clash with the vision that Stig and
> some others over at pear-dev had about PECL. Anyways, I don't really
> care about PECL much at the moment and thus won't invest to much energy
> in this discussion ;-).
The vision is
> Again: This point of view seems to clash with the vision that Stig and
> some others over at pear-dev had about PECL. Anyways, I don't really
> care about PECL much at the moment and thus won't invest to much energy
> in this discussion ;-).
The vision is different for everyone it seems. Last I
On Fri, 2003-04-04 at 19:35, Sterling Hughes wrote:
> On Fri, 2003-04-04 at 12:42, Martin Jansen wrote:
> > On Fri, 2003-04-04 at 19:15, Sterling Hughes wrote:
> > > On Fri, 2003-04-04 at 12:26, Martin Jansen wrote:
> > > > "In PECL all code has to follow the PHP coding standards."
> > > > (http://
oseph
> -Original Message-
> From: Tom Sommer [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 04, 2003 2:05 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [PHP-DEV] If you want to avoid annoying CS commits
>
>
> On Fri, 4 Apr 2003 12:11:16 -0500, Joseph Tate wrote:
>
>
On Fri, 4 Apr 2003 12:11:16 -0500, Joseph Tate wrote:
> How about documenting an astyle (insert stylizing app of choice here) line
> in CODING_STANDARDS that people can run on their code to make it conform to
> said standards.
What astyle would you suggest?
--
Tom Sommer, Denmark
www.tsn.dk - w
> The difference between 'pushing' and 'encouraging' is tought in
> management school. The semantical difference is NULL.
Derick, you need to realize that you lack authority. Someone
without authority cannot push anything what so ever.
Or to put it differently:
A bully pushes.
On Fri, 4 Apr 2003, Sascha Schumann wrote:
> > I'm not setting any rules, I'm just trying to push ways of effective
> > collaboration due to the adoption of the same standards for everbody.
>
> You are in no position to push anything.
>
> Try 'encouraging' or 'convincing' the next time.
> Also developing PHP extensions is much different than developing PHP.
> In PHP extensions the code itself is much more encapsulated, in PECL
> individual package development is encapsulated. As long as the code
> follows the php naming conventions (for exported functions), it can
> interact nic
On Fri, 2003-04-04 at 12:42, Martin Jansen wrote:
> On Fri, 2003-04-04 at 19:15, Sterling Hughes wrote:
> > On Fri, 2003-04-04 at 12:26, Martin Jansen wrote:
> > > "In PECL all code has to follow the PHP coding standards."
> > > (http://pear.php.net/manual/en/developers.meaning.php)
> > >
> >
> >
> I'm not setting any rules, I'm just trying to push ways of effective
> collaboration due to the adoption of the same standards for everbody.
You are in no position to push anything.
Try 'encouraging' or 'convincing' the next time.
- Sascha
--
PHP Internals - PHP Runtime Developme
On Fri, 4 Apr 2003, Sascha Schumann wrote:
> Derick, your attempts at setting rules are misguided.
I'm not setting any rules, I'm just trying to push ways of effective
collaboration due to the adoption of the same standards for everbody.
Derick
--
"
On Fri, 2003-04-04 at 19:15, Sterling Hughes wrote:
> On Fri, 2003-04-04 at 12:26, Martin Jansen wrote:
> > "In PECL all code has to follow the PHP coding standards."
> > (http://pear.php.net/manual/en/developers.meaning.php)
> >
>
> Then the manual is wrong.
Oh, come on: You should have come
On Fri, 2003-04-04 at 12:26, Martin Jansen wrote:
> On Fri, 2003-04-04 at 18:26, Sterling Hughes wrote:
> > No, in PEAR. In PECL your code can look however it likes, at least
> > that's my understanding.
>
> The manual states it differently:
>
> "In PECL all code has to follow the PHP coding sta
On Fri, 2003-04-04 at 18:26, Sterling Hughes wrote:
> No, in PEAR. In PECL your code can look however it likes, at least
> that's my understanding.
The manual states it differently:
"In PECL all code has to follow the PHP coding standards."
(http://pear.php.net/manual/en/developers.meaning.php)
Derick, your attempts at setting rules are misguided.
- Sascha
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Fri, 4 Apr 2003, Sascha Schumann wrote:
> I barked at Derick for trying to police me with his docref
> pet stuff.
1. It's not my stuff
2. I'm not particulairy fond of it either, but that doesn't mean I don't
use it in my code for the PHP project.You may object or not, but if
it
erling Hughes [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 04, 2003 11:45 AM
> To: Sascha Schumann
> Cc: [EMAIL PROTECTED]
> Subject: Re: [PHP-DEV] If you want to avoid annoying CS commits
>
>
> On Fri, 2003-04-04 at 11:54, Sascha Schumann wrote:
> > Sterling, you are m
Sterling Hughes <[EMAIL PROTECTED]> wrote:
>
> Ahh, well, you should follow the coding standards regardless, or rather
> change them. I've just removed docref and assert bogusness from the
> files, so, in that case, you are no longer in violation. (you should
> throw a party. ;-)
Hmm, I partly a
On Fri, 2003-04-04 at 11:54, Sascha Schumann wrote:
> Sterling, you are missing some important points here.
>
> > Geeze Luise, its not that hard, and the coding standards are there for a
> > (good) reason. If you object to some of the standards, discuss that,
>
> If you look at my code,
Sterling, you are missing some important points here.
> Geeze Luise, its not that hard, and the coding standards are there for a
> (good) reason. If you object to some of the standards, discuss that,
If you look at my code, 99% of it follows the coding styles,
because I've adopted th
On Fri, 2003-04-04 at 11:45, Lukas Smith wrote:
> > From: Sterling Hughes [mailto:[EMAIL PROTECTED]
> > Sent: Friday, April 04, 2003 6:09 PM
>
> > Geeze Luise, its not that hard, and the coding standards are there for
> a
> > (good) reason. If you object to some of the standards, discuss that,
>
> From: Sterling Hughes [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 04, 2003 6:09 PM
> Geeze Luise, its not that hard, and the coding standards are there for
a
> (good) reason. If you object to some of the standards, discuss that,
> but the source code should follow a unified style: we have a
22 matches
Mail list logo
