On 28 January 2004 15:52, Cesar Cordovez wrote:
> Jay Blanchard wrote:
> > I think that you meant to "its already been broughten!", didn't
> > you? Did you know that you will find that bracing style has been
> > debated since the days of FORTRAN?
>
>
> Oh! Fortran 77! I remember those times! =)
Jay Blanchard wrote:
I think that you meant to "its already been broughten!", didn't you? Did
you know that you will find that bracing style has been debated since
the days of FORTRAN?
Oh! Fortran 77! I remember those times! =) And I still think inline
braces wins hands down!!!
Cesar
--
PHP
[snip]
>>Its all good, it's like inline braces versus dropped braces and every
>>other coding style debate :) There's no winner.
>
> pfft. Inline braces wins hands down ;p
It's on now. Somebody set up the ring for the cage match. Last brace
standing at the end wins. ;)
[/snip]
I think that yo
Jeremy wrote:
[snip]
Its all good, it's like inline braces versus dropped braces and every
other coding style debate :) There's no winner.
[/snip]
pfft. Inline braces wins hands down ;p
-J
It's on now. Somebody set up the ring for the cage match. Last brace
standing at the end wins. ;)
--
B
Chris Shiflett wrote:
And your file sizes increase by 25%, and you enforce your tab preference
on every other developer (rather than letting them choose their own), and
you'd better hope that everyone's editor can perform operations on
vertical selections of text, otherwise changes in identation b
[snip]
>Its all good, it's like inline braces versus dropped braces and every
>other coding style debate :) There's no winner.
[/snip]
pfft. Inline braces wins hands down ;p
-J
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
On Tue, 2004-01-27 at 13:49, Chris Shiflett wrote:
> --- Robert Cummings <[EMAIL PROTECTED]> wrote:
> > Event better... turn your editor's tab character to 4 spaces, then
> > your code never contains those despicable tab characters and you won't
> > accidentally insert tabs into strings :)
>
> And
--- Alex Pilson <[EMAIL PROTECTED]> wrote:
> Couldn't you trim the items before placing into an array?
That would not have helped him, because trim() doesn't remove any
whitespace in between characters.
Chris
=
Chris Shiflett - http://shiflett.org/
PHP Security Handbook
Coming mid-2004
--- Robert Cummings <[EMAIL PROTECTED]> wrote:
> Event better... turn your editor's tab character to 4 spaces, then
> your code never contains those despicable tab characters and you won't
> accidentally insert tabs into strings :)
And your file sizes increase by 25%, and you enforce your tab pref
At 1:40 PM -0500 1/27/04, Robert Cummings wrote:
On Tue, 2004-01-27 at 09:19, Jay Blanchard wrote:
When constructing arrays where you are meddling with fixed width
substrings in a larger file make sure that the array item does not
contain a tab or you will certainly get unexpected results;
$arr
On Tue, 2004-01-27 at 09:19, Jay Blanchard wrote:
> When constructing arrays where you are meddling with fixed width
> substrings in a larger file make sure that the array item does not
> contain a tab or you will certainly get unexpected results;
>
> $arrBadInfo (
> 'AMARILLOHOUSE ',
>
When constructing arrays where you are meddling with fixed width
substrings in a larger file make sure that the array item does not
contain a tab or you will certainly get unexpected results;
$arrBadInfo (
'AMARILLOHOUSE ',
'KJONES HOUSE ', <--- 16 characters wide, or is it?
12 matches
Mail list logo
