|
|
Posted by Steve on 09/13/07 05:11
"Jerry Stuckle" <jstucklex@attglobal.net> wrote in message
news:UOednTt_JMQuNHXbnZ2dnUVZ_qKgnZ2d@comcast.com...
> Steve wrote:
>>> Not at all. OK, on a Windows system MySQL support is supplied by
>>> php_mysql.dll. And if MySQL isn't installed, the DLL won't load and
>>> phpinfo() will show MySQL support isn't enabled.
>>>
>>> The MySQL interface is NOT compiled into PHP on the distributed Windows
>>> binaries - or you'd never be able to run PHP unless you had MySQL
>>> installed.
>>
>> again, you brought up the mysql example. i'm keeping this generic and
>> modules like .net and others can certainly be compiled directly into php.
>>
>
> Nope, I just corrected your misstatements about PHP and MySQL. It is
> typical of the way PHP modules act. Other modules act the same way.
and other modules at the same time do NOT act the same way, but in the way i
described. since you won't get off the mysql specifics theme and refuse to
see my "misstatements" at the conceptual level i intended...let's talk about
ODBC and php. i can "enable" odbc in php. however i do that is beside the
point. that main thing to note is that the "enabling" doesn't require *ANY*
db to be installed...since there is NO *literal* ODBC database. odbc is a
protocol, not a database. so your point about having to have third party
applications installed for every lib/extension that may consume them carries
no weight. *SOME* extensions are protocols, some are functional resources,
and some are just type libraries. in the case of .net enabling, it is a set
of functional resources that php to use the .net framework. that does NOT
mean that phpinfo() would show different results when the same compiled
version of php gets put on a server with the .net framework and on one
without. it shows "enabled" in both cases.
try it. until then, you have an unqualified "Nope". after you do, as i have
done this evening, your "Nope" will turn to an "Oh...Ok, Ooops".
>> now to say that i have to have mysql (specifically) installed on my
>> system that runs php and enables php is rather odd since i should be able
>> to connect to any server running mysql if i provide the proper
>> credentials, etc.. for this specific mysql lib, you're saying the
>> dependency is an absolute must (that i have to have mysql installed on
>> the same server though i otherwise have NO intention of ever using it)?
>> can you tell me you've actually *done* this in order to prove it to
>> yourself before? do you have a documented reference to support this?
>>
>
> You need to have the MySQL client libraries installed on the system
> running PHP - just like if it were MSSQL Oracle or any other module. So
> yes, the dependency is an absolute must.
omg! you weren't even paying attention. the way in which php is compile or
whether or not modules exist IS NOT EVEN THE POINT!!! i already explained
that the "libraries" are indeed needed if the extension is not able to be
compiled into php!
read the OP. he wanted to know:
"And I'm wondering why PHP says .net support = enabled where .net is NOT
installed."
are you just arguing with me for the sake of arguing?!!! my point is that
ENABLING a feature in php has NOTHING to do with whether or not the TARGET
(.net framework in this case) is installed. i never disagreed with "client
libraries", in fact i specifically stated how php could include features
(compilation or run-time loading) and even states precisely that the
extension in question MUST exist in order to either compile it in or load at
run-time. did you miss that whole thread?
> You need to learn how these modules work. It's not just PHP - the same is
> true in C/C++, for instance.
i know how they do. it just seems you haven't even been on the same topic.
i'm talking about third-party applications and you're talking about
libraries that make it possible for php to use them.
<snip>
> Great. Now try to get it to work when the COM module you're calling isn't
> installed on the system. Or the new vendor when you don't have the DLL
> installed.
Great. now try and follow a thread, see what was asked, and THEN judge the
answer. you're not even in the ball park as far as this topic is concerned.
am i going to hear back from you on this post? i'd be embarrassed to had i
done the same thing. but it takes a certain kind of person to step back from
such a defensive position as you've taken and say that, indeed, "i just
misunderstood what you were explaining".
we'll see.
Navigation:
[Reply to this message]
|