, int, $memo, varchar(1000) )
or die(Invalid input!);
// code...
}
-Original Message-
From: Dr. Evil [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 12, 2001 10:31 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP] The need for strong typing...
The one
, because a
designer (for example) couldnt accidentally open your page in a wysiwymg
editor and kill parts of your app.
my addt .02
q.
-Original Message-
From: Opec Kemp [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 12, 2001 9:17 PM
To: Dr. Evil
Cc: PHP List
Subject: RE: [PHP] The need
The one problem with all your musings is that there is no such thing as an
integer when it comes to transferring data over http. Everything comes as
a string. What is done with these strings when they get to the
application is what matters. It's not like there is an HTML form element
like
If you were writing rigorous financial applications, I would hope you were
doing enough testing and checking that things like that didn't happen in the
first place.
You shouldn't be lazy and rely on the language to correct your mistakes.
Strong typing only gets in the way (w/ PHP at least),
The one problem with all your musings is that there is no such thing as an
integer when it comes to transferring data over http. Everything comes as
a string. What is done with these strings when they get to the
application is what matters. It's not like there is an HTML form element
like
I was going to write a whole diatribe, venting rage, trying to
prove you wrong etc, etc... and then I got to the last paragraph
and realised we probably actually agreed:
This doesn't mean that PHP should be changed to allow strong typing.
It may mean though that PHP isn't the right language for
Also obviously, this capability isn't needed for most of what PHP is
used for, and so maybe it doesn't belong in PHP, and maybe those of us
who are writing more sensitive aps should look into other things. Any
sugestions?
I suppose that if you *really* do need strongly typed language that's
I was going to write a whole diatribe, venting rage, trying to
prove you wrong etc, etc... and then I got to the last paragraph
and realised we probably actually agreed:
Yes, I think so too. Different languages for different things. Even
COBOL has a valid reason for existing. In fact, most
I will look into JSP.
Even on the same website, we could have two different languages: Maybe
we'll use JSP for the transaction stuff, and PHP for customer support
pages, where things are less critical.
Incidentally, PHP4 can also use some Java Serverlet or Bean. Check out this
bit from the
9 matches
Mail list logo
