Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.php > #10837 > unrolled thread

part 2 - file exists not working

Back to article view | Back to comp.lang.php

Contents

  part 2 - file exists not working richard <noreply@example.com> - 2013-09-23 10:04 -0400
    Re: part 2 - file exists not working Tim Streater <timstreater@greenbee.net> - 2013-09-23 15:17 +0100
      Re: part 2 - file exists not working richard <noreply@example.com> - 2013-09-23 10:35 -0400
    Re: part 2 - file exists not working Paul Herber <paul@pherber.com> - 2013-09-23 15:33 +0100
    Re: part 2 - file exists not working David Robley <me@home.invalid> - 2013-09-24 10:16 +0930
      Re: part 2 - file exists not working Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2013-09-23 22:07 -0400
        Re: part 2 - file exists not working richard <noreply@example.com> - 2013-09-24 01:57 -0400
          Re: part 2 - file exists not working David Robley <me@home.invalid> - 2013-09-24 17:19 +0930
            Re: part 2 - file exists not working richard <noreply@example.com> - 2013-09-24 04:10 -0400
            Re: part 2 - file exists not working richard <noreply@example.com> - 2013-09-24 04:32 -0400
            Re: part 2 - file exists not working Doug Miller <doug_at_milmac_dot_com@example.com> - 2013-09-24 23:23 +0000
              Re: part 2 - file exists not working David Robley <me@home.invalid> - 2013-09-25 09:48 +0930
          Re: part 2 - file exists not working Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2013-09-24 09:45 -0400
            Re: part 2 - file exists not working Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-09-24 16:34 +0200
              Re: part 2 - file exists not working Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2013-09-24 10:41 -0400
                Re: part 2 - file exists not working richard <noreply@example.com> - 2013-09-24 12:17 -0400
                  Re: part 2 - file exists not working Richard Yates <richard@yatesguitar.com> - 2013-09-24 09:29 -0700
                    Re: part 2 - file exists not working Twayne <nobody@spamcop.net> - 2013-09-24 18:51 -0400
                  Re: part 2 - file exists not working Denis McMahon <denismfmcmahon@gmail.com> - 2013-09-24 19:10 +0000
                    Re: part 2 - file exists not working Twayne <nobody@spamcop.net> - 2013-09-24 19:08 -0400
                      Re: part 2 - file exists not working Richard Yates <richard@yatesguitar.com> - 2013-09-24 18:39 -0700
                        Re: part 2 - file exists not working "Peter H. Coffin" <hellsop@ninehells.com> - 2013-09-24 22:17 -0500
                        Re: part 2 - file exists not working Twayne <nobody@spamcop.net> - 2013-09-26 17:20 -0400
                          Re: part 2 - file exists not working Richard Yates <richard@yatesguitar.com> - 2013-09-26 15:43 -0700
                            Re: part 2 - file exists not working Jerry Stuckle <jstucklex@attglobal.net> - 2013-09-26 19:43 -0400
                      Re: part 2 - file exists not working Scott Johnson <noonehome@chalupasworld.com> - 2013-09-24 18:54 -0700
                        Re: part 2 - file exists not working Twayne <nobody@spamcop.net> - 2013-09-26 17:39 -0400
                          Re: part 2 - file exists not working Richard Yates <richard@yatesguitar.com> - 2013-09-26 15:47 -0700
                            Re: part 2 - file exists not working Twayne <nobody@spamcop.net> - 2013-09-28 13:58 -0400
                              Re: part 2 - file exists not working Richard Yates <richard@yatesguitar.com> - 2013-09-28 11:45 -0700
                      Re: part 2 - file exists not working Tim Streater <timstreater@greenbee.net> - 2013-09-25 09:01 +0100
                Re: part 2 - file exists not working Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-09-24 18:54 +0200
                  Re: part 2 - file exists not working Tim Streater <timstreater@greenbee.net> - 2013-09-24 18:30 +0100
                Re: part 2 - file exists not working Scott Johnson <noonehome@chalupasworld.com> - 2013-09-24 15:40 -0700
                  Re: part 2 - file exists not working Twayne <nobody@spamcop.net> - 2013-09-24 19:14 -0400
                    Re: part 2 - file exists not working Richard Yates <richard@yatesguitar.com> - 2013-09-24 18:43 -0700
                      Re: part 2 - file exists not working Twayne <nobody@spamcop.net> - 2013-09-26 17:42 -0400
                Re: part 2 - file exists not working Twayne <nobody@spamcop.net> - 2013-09-24 18:50 -0400
                  Re: part 2 - file exists not working Scott Johnson <noonehome@chalupasworld.com> - 2013-09-24 18:56 -0700
                  Re: part 2 - file exists not working Curtis Dyer <dyer85@gmail.com> - 2013-09-26 06:01 +0000
                    Re: part 2 - file exists not working Twayne <nobody@spamcop.net> - 2013-09-26 18:04 -0400
                      Re: part 2 - file exists not working Curtis Dyer <dyer85@gmail.com> - 2013-09-27 01:47 +0000
                        Re: part 2 - file exists not working Jerry Stuckle <jstucklex@attglobal.net> - 2013-09-26 22:56 -0400
                          Re: part 2 - file exists not working Richard Yates <richard@yatesguitar.com> - 2013-09-26 20:11 -0700
                            Re: part 2 - file exists not working Jerry Stuckle <jstucklex@attglobal.net> - 2013-09-26 23:41 -0400
                          Re: part 2 - file exists not working Curtis Dyer <dyer85@gmail.com> - 2013-09-27 06:04 +0000
                        OT Re: part 2 - file exists not working Twayne <nobody@spamcop.net> - 2013-09-28 14:33 -0400
                          Re: OT Re: part 2 - file exists not working Fiver <numeralfive@gmail.com> - 2013-09-28 23:12 +0200
                            Re: OT Re: part 2 - file exists not working The Natural Philosopher <tnp@invalid.invalid> - 2013-09-29 06:50 +0100
                              Re: OT Re: part 2 - file exists not working "Peter H. Coffin" <hellsop@ninehells.com> - 2013-09-29 10:39 -0500
                                Re: OT Re: part 2 - file exists not working Jerry Stuckle <jstucklex@attglobal.net> - 2013-09-29 14:49 -0400
    Re: part 2 - file exists not working Doug Miller <doug_at_milmac_dot_com@example.com> - 2013-09-24 23:20 +0000
      Re: part 2 - file exists not working Richard Yates <richard@yatesguitar.com> - 2013-09-24 18:46 -0700
      Re: part 2 - file exists not working richard <noreply@example.com> - 2013-09-24 22:27 -0400
        Re: part 2 - file exists not working The Natural Philosopher <tnp@invalid.invalid> - 2013-09-25 06:21 +0100
        Re: part 2 - file exists not working David Robley <me@home.invalid> - 2013-09-25 15:20 +0930
          Re: part 2 - file exists not working Doug Miller <doug_at_milmac_dot_com@example.com> - 2013-09-26 20:30 +0000
      Re: part 2 - file exists not working Denis McMahon <denismfmcmahon@gmail.com> - 2013-09-25 07:42 +0000
        Re: part 2 - file exists not working The Natural Philosopher <tnp@invalid.invalid> - 2013-09-25 09:07 +0100
          Re: part 2 - file exists not working Richard Yates <richard@yatesguitar.com> - 2013-09-25 06:29 -0700
            Re: part 2 - file exists not working The Natural Philosopher <tnp@invalid.invalid> - 2013-09-25 15:09 +0100

Page 3 of 4 — ← Prev page 1 2 [3] 4  Next page →

#10912

On 2013-09-26 2:01 AM, Curtis Dyer wrote:
...

>
> Arbitrary server admins don't determine when features of PHP
> become deprecated, the PHP development team does.

Say WHAT?
  ... what makes you think that current servers, which almost all offer 
at least TWO versions of PHP to its users will stop doing that? Some 
even offer THREE I've come across in the past.
    DEPRECATED means removed from a VERSION of the language, not ALL 
versions!

    And just who is going to force server admins to have a dictated 
version of PHP available and no other?

It's myopic crap-thinking like that, that gets my attention here. And 
besides, mysql i isn't all that different from mysql, period. It's just 
not the Armageddon arrival as some are working so hard to point out.
    If you want to help, TEACH ; otherwise phase out. Forget the vague 
warnings and scenarios of web sites not working overnight. You have a 
version of PHP SET for your site on any good server, and the appearance 
of a new version is NOT going to automatically be applied to your sites!!

...

> When giving people advice about writing code, it's helpful to
> encourage the best possible practices. The mysql extension is
> indeed deprecated, and people learning PHP ought to be made well
> aware of this.

True, and that should be your job; NOT making gregarious claims that all 
sites will stop working if/when a server's admin employs a new version 
of a program!
>
> While your code may continue to work on your system, the same
> cannot be said of everyone who takes advice from posts such as
> those in this thread.

THEN SAY SO! Quit hiding behind the depracated but I'll not impart any 
further comment mentaility!



>
> If you would like your code to be as correct and portable as
> possible--if you care at all about writing good code--why would
> you dismiss completely that an extension is deprecated?

Where did that come from? You mean using a different version, when the 
latest version provides NO improvements, should automatically be 
implemented? That's nonsense.

>
>> The scare tactics are silly and that's why people don't worry
>> about it.
>
> People are trying to provide helpful information. No one here is
> employing scare tactics.

No, they are not; they are employing ego-driven scare tactics and saying 
nothing but it's depracated - hell, in this whole thread the version 
number has never even been mentioned in any way -- why is THAT?
>

Cheers,

Twayne`

[toc] | [prev] | [next] | [standalone]

#10919

Twayne wrote:

[Twayne's quoted text below has been rewrapped]

> On 2013-09-26 2:01 AM, Curtis Dyer wrote: ...
> 
>> Arbitrary server admins don't determine when features of PHP
>> become deprecated, the PHP development team does.
> 
> Say WHAT?  ... what makes you think that current servers, which
> almost all offer at least TWO versions of PHP to its users will
> stop doing that?

None of what I wrote has anything to do with this.

> Some even offer THREE I've come across in the past.  DEPRECATED
> means removed from a VERSION of the language, not ALL versions!

No, deprecated means that a feature or practice is considered 
dated in favor of something else, and that one should avoid using 
it, where possible. It is by no means a strict mandate that you 
must never use the feature. (Although, you obviously can't use the 
feature whenever you move to the new version in which a deprecated 
feature is dropped.)

> And just who is going to force server admins to have a dictated
> version of PHP available and no other?

No one, but I never wrote or implied anything like that.

> It's myopic crap-thinking like that, that gets my attention
> here. 

It's not a big deal. If you're writing new code, today, there's no 
reason not to avoid using the mysql extension. That's all. I'm not 
warning to toss away or fix old code *right now*.

And, if anything, it's myopic thinking to write code depending on 
a deprecated extension in situations where you don't need to.

> And besides, mysql i isn't all that different from mysql,
> period. It's just not the Armageddon arrival as some are working
> so hard to point out. 

This is a ridiculous straw man.

> If you want to help, TEACH ; otherwise phase out.

What do you mean? What do you think trying to inform people about 
best practices is all about? No one here is imposing mandates on 
anyone. We can just offer the best advice as we're able, and it's 
up to the OP and others who might read the advice to do with it 
what they will.

> Forget the vague warnings and scenarios of web sites not working
> overnight.

No one has written this. When I read Thomas's post upthread, for 
example, it read as a helpful aside to me. It was quite clear and 
concise. There's nothing vague about informing people about a 
deprecated feature.

Again, no one has written that people's code will break overnight.

<snip>

>> When giving people advice about writing code, it's helpful to
>> encourage the best possible practices. The mysql extension is
>> indeed deprecated, and people learning PHP ought to be made
>> well aware of this.
> 
> True, and that should be your job;

Usenet is not my job; Usenet contributors don't get paid for 
posting. I generally post here in the event that I feel I'm able 
to provide what little help I can. Further, newsgroups like this 
have been a big help to me, so contributing back is a nice change 
of pace.

> NOT making gregarious claims

I've never heard claims described as gregarious. Perhaps you meant 
grandiose? If that's the case, I made none.

The mysql extension is deprecated, but this has nothing to do with 
magically breaking Web servers. It's a simple warning to 
developers (and sever admins), that, at some point, the extension 
will be phased out.

It's a helpful warning and is intended to give people time to 
prepare however they choose. For some people, the concern probably 
isn't immediate. That's fine. However, there's absolutely nothing 
wrong with suggesting to beginners that they ought to use instead 
mysqli or the PDO MySQL driver.

There are other reasons for using alternatives to the mysql 
extension that go beyond the fact that it's deprecated (although, 
they likely have contributed to the fact that it has become 
deprecated). For example, the fact that you can use prepared 
statements or, in PDO's case, it provides an abstract interface to 
allow developers to reuse code for multiple databases.

> that all sites will stop working if/when a server's admin
> employs a new version of a program!
>>
>> While your code may continue to work on your system, the same
>> cannot be said of everyone who takes advice from posts such as
>> those in this thread.
> 
> THEN SAY SO!

I have written it in the post you quoted. Although, I didn't write 
in all-caps, so perhaps you missed it.

<snip>

-- 
Curtis Dyer
<?$x='<?$x=%c%s%c;printf($x,39,$x,39);?>';printf($x,39,$x,39);?>

[toc] | [prev] | [next] | [standalone]

#10920

On 9/26/2013 9:47 PM, Curtis Dyer wrote:
> Twayne wrote:
>
> [Twayne's quoted text below has been rewrapped]
>
>> On 2013-09-26 2:01 AM, Curtis Dyer wrote: ...
>>
>>> Arbitrary server admins don't determine when features of PHP
>>> become deprecated, the PHP development team does.
>>
>> Say WHAT?  ... what makes you think that current servers, which
>> almost all offer at least TWO versions of PHP to its users will
>> stop doing that?
>
> None of what I wrote has anything to do with this.
>
>> Some even offer THREE I've come across in the past.  DEPRECATED
>> means removed from a VERSION of the language, not ALL versions!
>
> No, deprecated means that a feature or practice is considered
> dated in favor of something else, and that one should avoid using
> it, where possible. It is by no means a strict mandate that you
> must never use the feature. (Although, you obviously can't use the
> feature whenever you move to the new version in which a deprecated
> feature is dropped.)
>
>> And just who is going to force server admins to have a dictated
>> version of PHP available and no other?
>
> No one, but I never wrote or implied anything like that.
>
>> It's myopic crap-thinking like that, that gets my attention
>> here.
>
> It's not a big deal. If you're writing new code, today, there's no
> reason not to avoid using the mysql extension. That's all. I'm not
> warning to toss away or fix old code *right now*.
>
> And, if anything, it's myopic thinking to write code depending on
> a deprecated extension in situations where you don't need to.
>
>> And besides, mysql i isn't all that different from mysql,
>> period. It's just not the Armageddon arrival as some are working
>> so hard to point out.
>
> This is a ridiculous straw man.
>
>> If you want to help, TEACH ; otherwise phase out.
>
> What do you mean? What do you think trying to inform people about
> best practices is all about? No one here is imposing mandates on
> anyone. We can just offer the best advice as we're able, and it's
> up to the OP and others who might read the advice to do with it
> what they will.
>
>> Forget the vague warnings and scenarios of web sites not working
>> overnight.
>
> No one has written this. When I read Thomas's post upthread, for
> example, it read as a helpful aside to me. It was quite clear and
> concise. There's nothing vague about informing people about a
> deprecated feature.
>
> Again, no one has written that people's code will break overnight.
>
> <snip>
>
>>> When giving people advice about writing code, it's helpful to
>>> encourage the best possible practices. The mysql extension is
>>> indeed deprecated, and people learning PHP ought to be made
>>> well aware of this.
>>
>> True, and that should be your job;
>
> Usenet is not my job; Usenet contributors don't get paid for
> posting. I generally post here in the event that I feel I'm able
> to provide what little help I can. Further, newsgroups like this
> have been a big help to me, so contributing back is a nice change
> of pace.
>
>> NOT making gregarious claims
>
> I've never heard claims described as gregarious. Perhaps you meant
> grandiose? If that's the case, I made none.
>
> The mysql extension is deprecated, but this has nothing to do with
> magically breaking Web servers. It's a simple warning to
> developers (and sever admins), that, at some point, the extension
> will be phased out.
>
> It's a helpful warning and is intended to give people time to
> prepare however they choose. For some people, the concern probably
> isn't immediate. That's fine. However, there's absolutely nothing
> wrong with suggesting to beginners that they ought to use instead
> mysqli or the PDO MySQL driver.
>
> There are other reasons for using alternatives to the mysql
> extension that go beyond the fact that it's deprecated (although,
> they likely have contributed to the fact that it has become
> deprecated). For example, the fact that you can use prepared
> statements or, in PDO's case, it provides an abstract interface to
> allow developers to reuse code for multiple databases.
>
>> that all sites will stop working if/when a server's admin
>> employs a new version of a program!
>>>
>>> While your code may continue to work on your system, the same
>>> cannot be said of everyone who takes advice from posts such as
>>> those in this thread.
>>
>> THEN SAY SO!
>
> I have written it in the post you quoted. Although, I didn't write
> in all-caps, so perhaps you missed it.
>
> <snip>
>

Curtis,

Please don't feed the troll...


-- 
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#10921

On Thu, 26 Sep 2013 22:56:49 -0400, Jerry Stuckle
<jstucklex@attglobal.net> wrote:

>Curtis,
>
>Please don't feed the troll...

Disagree with the characterization. Trolls post solely to provoke
responses as a kind of vandalism. Twayne has posted genuine questions
here. He certainly is stuck on this issue and has greatly mispercieved
the posts on the topic, but there is no reason to think that he is
being disingenuous.

[toc] | [prev] | [next] | [standalone]

#10922

On 9/26/2013 11:11 PM, Richard Yates wrote:
> On Thu, 26 Sep 2013 22:56:49 -0400, Jerry Stuckle
> <jstucklex@attglobal.net> wrote:
>
>> Curtis,
>>
>> Please don't feed the troll...
>
> Disagree with the characterization. Trolls post solely to provoke
> responses as a kind of vandalism. Twayne has posted genuine questions
> here. He certainly is stuck on this issue and has greatly mispercieved
> the posts on the topic, but there is no reason to think that he is
> being disingenuous.
>

You haven't read his posts very closely, then.  Examples:

Curtis Dyer:

When giving people advice about writing code, it's helpful to
encourage the best possible practices. The mysql extension is
indeed deprecated, and people learning PHP ought to be made well
aware of this.

Twayne:

True, and that should be your job; NOT making gregarious claims that all 
sites will stop working if/when a server's admin employs a new version 
of a program!

(which Curtis NEVER claimed)

And later in that same post:

Twayne:
The scare tactics are silly and that's why people don't worry
about it.

Curtis Dyer:
People are trying to provide helpful information. No one here is
employing scare tactics.

Twayne:
No, they are not; they are employing ego-driven scare tactics and saying 
nothing but it's depracated - hell, in this whole thread the version 
number has never even been mentioned in any way -- why is THAT?

(But then ANYONE who disagrees with Twayne has an ego problem).

There are others - I'll leave them to you to find.  I'm not going to 
repeat everything he said in this thread.

And he's a well-known troll from other threads in this newsgroup, also.


-- 
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#10923

Jerry Stuckle wrote:

> On 9/26/2013 9:47 PM, Curtis Dyer wrote:
>> Twayne wrote:
>>
>> [Twayne's quoted text below has been rewrapped]
>>
>>> On 2013-09-26 2:01 AM, Curtis Dyer wrote: ...

<snip>

>>> And besides, mysql i isn't all that different from mysql,
>>> period. It's just not the Armageddon arrival as some are
>>> working so hard to point out.
>>
>> This is a ridiculous straw man.

<snip similar exchanges>

> Curtis,
> 
> Please don't feed the troll...

I try to resort to the killfile as a last resort, so assumed the 
best in this case. I merely wanted to clear up my points just to be 
certain; I've seen too many misunderstandings via textual 
communication.

Regardless, I can't be any clearer than I am now, and won't be 
provoked into a prolonged argument.

I see where you're coming from, though.

-- 
Curtis Dyer
<?$x='<?$x=%c%s%c;printf($x,39,$x,39);?>';printf($x,39,$x,39);?>

[toc] | [prev] | [next] | [standalone]

#10926 — OT Re: part 2 - file exists not working

You deserve respect and I am NOT trying to take that, or credibility 
away from you. That said, I do have a couple of observations if you will:


On 2013-09-26 9:47 PM, Curtis Dyer wrote:
> Twayne wrote:
>
> [Twayne's quoted text below has been rewrapped]
>
>> On 2013-09-26 2:01 AM, Curtis Dyer wrote: ...
>>
>>> Arbitrary server admins don't determine when features of PHP
>>> become deprecated, the PHP development team does.
>>
>> Say WHAT?  ... what makes you think that current servers, which
>> almost all offer at least TWO versions of PHP to its users will
>> stop doing that?
>
> None of what I wrote has anything to do with this.

You also didn't offer any enlightenment on what you meant, nor the 
question.

If you are the author of the >>> comments above, then I think you did. 
Or do you consider the word "Arbitrary" as an out? Or that there can 
only be ONE meaning to PHP development team?
>
>> Some even offer THREE I've come across in the past.  DEPRECATED
>> means removed from a VERSION of the language, not ALL versions!
>
> No, deprecated means that a feature or practice

(IN A VERSION OF THE APP IN QUESTION)

  is considered
> dated in favor of something else, and that one should avoid using
> it, where possible.

Of course.


  It is by no means a strict mandate that you
> must never use the feature. (Although, you obviously can't use the
> feature whenever you move to the new version in which a deprecated
> feature is dropped.)
That's a little obvious, too. But, unlike many, they are trying to say 
that the latest versions with the deprecations is all that will suddenly 
be available! It's just not true.

>
>> And just who is going to force server admins to have a dictated
>> version of PHP available and no other?
>
> No one, but I never wrote or implied anything like that.
>
>> It's myopic crap-thinking like that, that gets my attention
>> here.
>
> It's not a big deal. If you're writing new code, today, there's no
> reason not to avoid using the mysql extension. That's all. I'm not
> warning to toss away or fix old code *right now*.

Perhaps not; I don't take names as a rule and only respond to words 
within a post. Most mail clients and readers should be able to aptly 
show just who the response is/was to.
>
> And, if anything, it's myopic thinking to write code depending on
> a deprecated extension in situations where you don't need to.

Not if you don't intend to use that particular version yet. Change-over 
will come slowly (it's been a slow boat from China so far) .  Being 
prepared and keeping track of the trends is definitely important. Anyone 
with a site they value at all should indeed be keeping track of trends 
AND where their server admin is; normally it's there to find.
>
>> And besides, mysql i isn't all that different from mysql,
>> period. It's just not the Armageddon arrival as some are working
>> so hard to point out.
>
> This is a ridiculous straw man.

No, it's not, really. I don't mean a couple of editor search & destroys 
will fix it all up, but it's not that complex unless you have spaghetti 
to start with. Actually, IMO, it's a bit simpler in many areas. I often 
don't see the "why" of changes that are made, but then I'm not one of 
the authors either. At the moment, the 'i' version doesn't offer me 
anything I need and answers very few of my "wants".  I really consider 
it a natural progression of "life".
>
>> If you want to help, TEACH ; otherwise phase out.
>
> What do you mean? What do you think trying to inform people about
> best practices is all about? No one here is imposing mandates on
> anyone. We can just offer the best advice as we're able, and it's
> up to the OP and others who might read the advice to do with it
> what they will.

I mean, the chosen few who are pushing the line about change now or 
suffer are not doing anyone any kind of assistance. Blind statements and 
warnings without meat just aren't taken seriously. If one wants to 
spread they word then they also include anm authentic, realistic link or 
two to support their statements. So far I only recall one poster who did 
that, but only after this prodding started.
>
>> Forget the vague warnings and scenarios of web sites not working
>> overnight.
>
> No one has written this. When I read Thomas's post upthread, for
> example, it read as a helpful aside to me. It was quite clear and
> concise. There's nothing vague about informing people about a
> deprecated feature.

Yes, it has been written and here in this thread. And I believe it IS 
vague when one makes such a statement without any kind of reference to a 
cite where factual information can be found.

>
> Again, no one has written that people's code will break overnight.

Yes, they have; at least twice it's been brought up, maybe more because 
there are some posts I mostly skip over or don't even read like those 
from stuckle; he's all troll and nothing more in my books now.
>
> <snip>
>
>>> When giving people advice about writing code, it's helpful to
>>> encourage the best possible practices. The mysql extension is
>>> indeed deprecated, and people learning PHP ought to be made
>>> well aware of this.
>>
>> True, and that should be your job;
>
> Usenet is not my job;

No, if you're going to participate on Usenet, forums or whatever, you 
make it your job to be helpful and prevent erroneous impressions. If you 
wish to  be paid for it, then I'm afraid you're in the wrong place.

...
>
> It's a helpful warning and is intended to give people time to
> prepare however they choose. For some people, the concern probably
> isn't immediate. That's fine. However, there's absolutely nothing
> wrong with suggesting to beginners that they ought to use instead
> mysqli or the PDO MySQL driver.

Agreed

...

Regards,

Twayne`

[toc] | [prev] | [next] | [standalone]

#10928 — Re: OT Re: part 2 - file exists not working

On 2013-09-28 20:33, Twayne wrote:
>>> Some even offer THREE I've come across in the past.  DEPRECATED
>>> means removed from a VERSION of the language, not ALL versions!
>>
>> No, deprecated means that a feature or practice
> 
> (IN A VERSION OF THE APP IN QUESTION)
[...]
> But, unlike many, they are trying to say that the latest versions
> with the deprecations is all that will suddenly be available! It's
> just not true.

Depreciation is not tied to any versions; the availability of a feature
and E_DEPRECATED warnings about its status are.

This seems to be the core of your misunderstanding. Depreciation of a
feature is unrelated to individual releases. When the PHP project
decides to deprecate mysql, it doesn't matter if you use an older or
newer version, if your version issues warnings or not, or even if you
use PHP at all - the status of the feature is always the same:
deprecated, will be removed in a future version.

What you do with this information is up to you. You've been warned by
people in this group (and by the PHP manual) not to use mysql_* for new
code. For some reason you decided to get all upset about it. As of
version 5.5, PHP itself is issuing E_DEPRECATED warnings about the mysql
extension. If your reaction is to turn the warnings off or rely on older
PHP versions, you're making a mistake. So your hoster is nice enough to
provide legacy PHP versions for you, fine, but even they will eventually
get tired of it.

Obligatory car analogy: when your "check engine" light is flashing,
would you just keep driving and put a sticker over it, or would you do
something about it?

> Change-over will come slowly (it's been a slow boat from China so far) .

Wonder why it's been so slow... could it be because some people can't be
bothered to upgrade their code for years and years?

regards,
5er

[toc] | [prev] | [next] | [standalone]

#10929 — Re: OT Re: part 2 - file exists not working

On 28/09/13 22:12, Fiver wrote:
> On 2013-09-28 20:33, Twayne wrote:
>
>
>> Change-over will come slowly (it's been a slow boat from China so far) .
>
> Wonder why it's been so slow... could it be because some people can't be
> bothered to upgrade their code for years and years?
>
Ask any COBOL and RPG programmer whether there is still work around..


> regards,
> 5er
>


-- 
Ineptocracy

(in-ep-toc’-ra-cy) – a system of government where the least capable to 
lead are elected by the least capable of producing, and where the 
members of society least likely to sustain themselves or succeed, are 
rewarded with goods and services paid for by the confiscated wealth of a 
diminishing number of producers.

[toc] | [prev] | [next] | [standalone]

#10931 — Re: OT Re: part 2 - file exists not working

On Sun, 29 Sep 2013 06:50:09 +0100, The Natural Philosopher wrote:
> On 28/09/13 22:12, Fiver wrote:
>> On 2013-09-28 20:33, Twayne wrote:
>>
>>
>>> Change-over will come slowly (it's been a slow boat from China so far) .
>>
>> Wonder why it's been so slow... could it be because some people can't be
>> bothered to upgrade their code for years and years?
>>
> Ask any COBOL and RPG programmer whether there is still work around..

Feh. The worst part is that there's a lot good to be said about modern
RPG, or even old RPG. The trick is getting to talk to something *other*
than databases

-- 
Usenet should require licenses; licenses that can be revoked.
              -- Abigail

[toc] | [prev] | [next] | [standalone]

#10932 — Re: OT Re: part 2 - file exists not working

On 9/29/2013 11:39 AM, Peter H. Coffin wrote:
> On Sun, 29 Sep 2013 06:50:09 +0100, The Natural Philosopher wrote:
>> On 28/09/13 22:12, Fiver wrote:
>>> On 2013-09-28 20:33, Twayne wrote:
>>>
>>>
>>>> Change-over will come slowly (it's been a slow boat from China so far) .
>>>
>>> Wonder why it's been so slow... could it be because some people can't be
>>> bothered to upgrade their code for years and years?
>>>
>> Ask any COBOL and RPG programmer whether there is still work around..
>
> Feh. The worst part is that there's a lot good to be said about modern
> RPG, or even old RPG. The trick is getting to talk to something *other*
> than databases
>

RPG was never meant to talk to other than databases.  It's original 
intent was to make it easy for non-programmers to generate reports from 
databases (which were pretty much flat files back in the 60's).

Of course it's changed with technology, but AFAIK it's still designed 
for non-programmers to easily generate reports.

I do admit it's been around 40 years since I've done any RPG 
programming, and don't remember much of what I did back then.

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#10867

richard <noreply@example.com> wrote in news:6tzjiffjaqy6.1rfg283mi0q9m.dlg@40tude.net:

> if ($go="go") {echo "x";}

Richard, how many times is this now that someone has had to remind you of the difference 
between = and == ?

[toc] | [prev] | [next] | [standalone]

#10872

On Tue, 24 Sep 2013 23:20:58 +0000 (UTC), Doug Miller
<doug_at_milmac_dot_com@example.com> wrote:

>richard <noreply@example.com> wrote in news:6tzjiffjaqy6.1rfg283mi0q9m.dlg@40tude.net:
>
>> if ($go="go") {echo "x";}
>
>Richard, how many times is this now that someone has had to remind you of the difference 
>between = and == ?

Please spell his name correctly ("richard").

Richard 
(Who also makes the same coding error often enough, but not publicly,
so far.)

[toc] | [prev] | [next] | [standalone]

#10875

On Tue, 24 Sep 2013 23:20:58 +0000 (UTC), Doug Miller wrote:

> richard <noreply@example.com> wrote in news:6tzjiffjaqy6.1rfg283mi0q9m.dlg@40tude.net:
> 
>> if ($go="go") {echo "x";}
> 
> Richard, how many times is this now that someone has had to remind you of the difference 
> between = and == ?


because it is one of those little things I keep forgetting.
Like a ; or some other minor syntax error.

[toc] | [prev] | [next] | [standalone]

#10881

On 25/09/13 03:27, richard wrote:
> On Tue, 24 Sep 2013 23:20:58 +0000 (UTC), Doug Miller wrote:
>
>> richard <noreply@example.com> wrote in news:6tzjiffjaqy6.1rfg283mi0q9m.dlg@40tude.net:
>>
>>> if ($go="go") {echo "x";}
>>
>> Richard, how many times is this now that someone has had to remind you of the difference
>> between = and == ?
>
>
> because it is one of those little things I keep forgetting.
> Like a ; or some other minor syntax error.
>
why domnt you remember that you forget these things and check for them 
FIRST like everyone else does.

-- 
Ineptocracy

(in-ep-toc’-ra-cy) – a system of government where the least capable to 
lead are elected by the least capable of producing, and where the 
members of society least likely to sustain themselves or succeed, are 
rewarded with goods and services paid for by the confiscated wealth of a 
diminishing number of producers.

[toc] | [prev] | [next] | [standalone]

#10882

richard wrote:

> On Tue, 24 Sep 2013 23:20:58 +0000 (UTC), Doug Miller wrote:
> 
>> richard <noreply@example.com> wrote in
>> news:6tzjiffjaqy6.1rfg283mi0q9m.dlg@40tude.net:
>> 
>>> if ($go="go") {echo "x";}
>> 
>> Richard, how many times is this now that someone has had to remind you of
>> the difference between = and == ?
> 
> 
> because it is one of those little things I keep forgetting.
> Like a ; or some other minor syntax error.

Here is a tip for you to manage this particular problem - reverse the order 
of the test values; if you forget an = you'll trigger a syntax error.

if ("go" = $go) {echo "x";} // triggers an error
if ("go" == $go) {echo "x";} // works as expected

-- 
Cheers
David Robley

System halted. There is NOTHING you can do.

[toc] | [prev] | [next] | [standalone]

#10908

David Robley <me@home.invalid> wrote in news:l1ttfv$nt8$1@news.albasani.net:

> richard wrote:
> 
>> On Tue, 24 Sep 2013 23:20:58 +0000 (UTC), Doug Miller wrote:
>> 
>>> richard <noreply@example.com> wrote in
>>> news:6tzjiffjaqy6.1rfg283mi0q9m.dlg@40tude.net:
>>> 
>>>> if ($go="go") {echo "x";}
>>> 
>>> Richard, how many times is this now that someone has had to remind you of
>>> the difference between = and == ?
>> 
>> 
>> because it is one of those little things I keep forgetting.
>> Like a ; or some other minor syntax error.
> 
> Here is a tip for you to manage this particular problem - reverse the order 
> of the test values; if you forget an = you'll trigger a syntax error.
> 
> if ("go" = $go) {echo "x";} // triggers an error

Predictable result: richard posts here asking why he's getting the error.

> if ("go" == $go) {echo "x";} // works as expected
> 
He can't remember the difference between = and ==, how do you expect him to remember 
that?

[toc] | [prev] | [next] | [standalone]

#10883

On Tue, 24 Sep 2013 23:20:58 +0000, Doug Miller wrote:

> richard <noreply@example.com> wrote in
> news:6tzjiffjaqy6.1rfg283mi0q9m.dlg@40tude.net:
> 
>> if ($go="go") {echo "x";}
> 
> Richard, how many times is this now that someone has had to remind you
> of the difference between = and == ?

I would try and count it, but I'm constrained by a 128 bit adder.

-- 
Denis McMahon, denismfmcmahon@gmail.com

[toc] | [prev] | [next] | [standalone]

#10885

On 25/09/13 08:42, Denis McMahon wrote:
> On Tue, 24 Sep 2013 23:20:58 +0000, Doug Miller wrote:
>
>> richard <noreply@example.com> wrote in
>> news:6tzjiffjaqy6.1rfg283mi0q9m.dlg@40tude.net:
>>
>>> if ($go="go") {echo "x";}
>>
>> Richard, how many times is this now that someone has had to remind you
>> of the difference between = and == ?
>
> I would try and count it, but I'm constrained by a 128 bit adder.
>
That's better than being bitten 128 times by an adder.

-- 
Ineptocracy

(in-ep-toc’-ra-cy) – a system of government where the least capable to 
lead are elected by the least capable of producing, and where the 
members of society least likely to sustain themselves or succeed, are 
rewarded with goods and services paid for by the confiscated wealth of a 
diminishing number of producers.

[toc] | [prev] | [next] | [standalone]

#10886

On Wed, 25 Sep 2013 09:07:13 +0100, The Natural Philosopher
<tnp@invalid.invalid> wrote:

>On 25/09/13 08:42, Denis McMahon wrote:
>> On Tue, 24 Sep 2013 23:20:58 +0000, Doug Miller wrote:
>>
>>> richard <noreply@example.com> wrote in
>>> news:6tzjiffjaqy6.1rfg283mi0q9m.dlg@40tude.net:
>>>
>>>> if ($go="go") {echo "x";}
>>>
>>> Richard, how many times is this now that someone has had to remind you
>>> of the difference between = and == ?
>>
>> I would try and count it, but I'm constrained by a 128 bit adder.
>>
>That's better than being bitten 128 times by an adder.

Except that adders do not constrain. Constrictors do. So he might
better have said "but I'm constrained by a long Python."

[toc] | [prev] | [next] | [standalone]

Page 3 of 4 — ← Prev page 1 2 [3] 4  Next page →

Back to top | Article view | comp.lang.php

csiph-web