On Mon, April 23, 2007 2:56 pm, Justin Frim wrote:
> Now that's a stupid example, but, you get the idea.
Well, we agree that it's a stupid example...
:-) :-) :-)
http://cdbaby.com/browse/from/lynch
Yeah, I get a buck. So?
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit:
On Mon, 2007-04-23 at 15:56 -0400, Justin Frim wrote:
> Edward Vermillion wrote:
>
> >
> > On Apr 21, 2007, at 6:35 PM, Justin Frim wrote:
> >
> >> I've always gone by the rule that if you're making software that
> >> other people will see or use, make it clean.
> >> Sometimes I'll "cheat" and s
Edward Vermillion wrote:
On Apr 21, 2007, at 6:35 PM, Justin Frim wrote:
I've always gone by the rule that if you're making software that
other people will see or use, make it clean.
Sometimes I'll "cheat" and stick a @ symbol in front of a line to
shut up errors and warnings for that part
[snip]
I don't really want to do a isset check for every index I have.
[/snip]
Premature optimization is the root of all evil. Checks like this will
take nanoseconds to check. Find another way to optimize, like writing
better SQL queries.
--
PHP General Mailing List (http://www.php.net/)
To un
On Sat, April 21, 2007 6:35 pm, Justin Frim wrote:
> Sometimes I'll "cheat" and stick a @ symbol in front of a line to shut
> up errors and warnings for that particular line, but usually I only do
> that for speed optimization. (ie. if it's in a short loop that cycles
> many times).
I don't think
On Sat, April 21, 2007 4:01 am, Ross wrote:
> A quick one this morning.
>
> When coding should I be trying to code so there are no notices or is
> it ok
> to turn them off.
>
> I don't really want to do a isset check for every index I have.
[dorothy voice]
Do you want to write good code, or bad c
On Apr 21, 2007, at 6:35 PM, Justin Frim wrote:
I've always gone by the rule that if you're making software that
other people will see or use, make it clean.
Sometimes I'll "cheat" and stick a @ symbol in front of a line to
shut up errors and warnings for that particular line, but usually I
I've always gone by the rule that if you're making software that other
people will see or use, make it clean.
Sometimes I'll "cheat" and stick a @ symbol in front of a line to shut
up errors and warnings for that particular line, but usually I only do
that for speed optimization. (ie. if it's i
: Saturday, April 21, 2007 7:17:35 AM
Subject: Re: [PHP] should I be looking to eliminate all notices?
On Apr 21, 2007, at 4:01 AM, Ross wrote:
> A quick one this morning.
>
> When coding should I be trying to code so there are no notices or
> is it ok
> to turn them off.
>
If yo
On Apr 21, 2007, at 4:01 AM, Ross wrote:
A quick one this morning.
When coding should I be trying to code so there are no notices or
is it ok
to turn them off.
If you don't mind writing code that contains errors, notices are
errors. Not serious, but it's not that hard to write code in
2007. 04. 21, szombat keltezéssel 10.17-kor Ross ezt írta:
> Should I care? Is it considered bad practice to just turn them off?
some people consider it bad practice, yes
I personally wouldn't say it is bad practice, but I am sure that in many
cases notices can help finding bugs in your code. So
> -Message d'origine-
> De : Ross [mailto:[EMAIL PROTECTED]
> Envoyé : samedi 21 avril 2007 11:18
> À : php-general@lists.php.net
> Objet : Re: [PHP] should I be looking to eliminate all notices?
>
> Should I care? Is it considered bad practice to just tur
Should I care? Is it considered bad practice to just turn them off?
""Zoltán Németh"" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> When coding I think it is better to turn error_reporting to E_ALL and
> try to write code that emits no notices.
>
> Of course there might be some
When coding I think it is better to turn error_reporting to E_ALL and
try to write code that emits no notices.
Of course there might be some notices left, which you decide not to care
about, in production notices should be turned off then
greets
Zoltán Németh
2007. 04. 21, szombat keltezéssel 10
14 matches
Mail list logo
