Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #15716 > unrolled thread
| Started by | Derek Turner <frderek@suremail.je> |
|---|---|
| First post | 2015-10-20 18:57 +0000 |
| Last post | 2015-11-01 08:31 -0500 |
| Articles | 8 on this page of 128 — 22 participants |
Back to article view | Back to comp.lang.php
Check for military time Derek Turner <frderek@suremail.je> - 2015-10-20 18:57 +0000
Re: Check for military time Derek Turner <frderek@suremail.je> - 2015-10-20 19:00 +0000
Re: Check for military time Richard Yates <richard@yatesguitar.com> - 2015-10-20 21:35 -0700
Re: Check for military time Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-10-21 16:12 -0400
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-10-21 22:38 -0400
Re: Check for military time Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-10-22 10:43 -0400
Re: Check for military time Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-10-22 10:48 -0400
Re: Check for military time Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-10-22 17:20 +0200
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-10-22 12:19 -0400
Re: Check for military time "Peter H. Coffin" <hellsop@ninehells.com> - 2015-10-22 15:32 -0500
Re: Check for military time Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-10-22 23:08 +0200
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-10-22 20:19 -0400
Re: Check for military time Matthew Carter <m@ahungry.com> - 2015-10-22 22:07 -0400
Re: Check for military time "Beauregard T. Shagnasty" <a.nony.mous@example.invalid> - 2015-10-23 02:26 +0000
Re: Check for military time Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-10-22 17:13 -0400
Re: Check for military time Tim Streater <timstreater@greenbee.net> - 2015-10-22 22:57 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-10-22 20:22 -0400
Re: Check for military time Tim Streater <timstreater@greenbee.net> - 2015-10-23 09:19 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-10-23 09:32 -0400
Re: Check for military time Tim Streater <timstreater@greenbee.net> - 2015-10-23 15:43 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-10-23 11:11 -0400
Re: Check for military time gordonb.nwjln@burditt.org (Gordon Burditt) - 2015-10-23 12:36 -0500
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-10-23 13:40 -0400
Re: Check for military time Tim Streater <timstreater@greenbee.net> - 2015-10-23 18:54 +0100
Re: Check for military time Norman Peelman <npeelman@cfl.rr.com> - 2015-10-23 22:44 -0400
Re: Check for military time Tim Streater <timstreater@greenbee.net> - 2015-10-24 10:32 +0100
Re: Check for military time Derek Turner <frderek@suremail.je> - 2015-10-24 11:41 +0000
Re: Check for military time Norman Peelman <npeelman@cfl.rr.com> - 2015-10-24 15:15 -0400
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-10-22 20:21 -0400
Re: Check for military time Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-10-22 20:38 -0400
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-10-22 20:47 -0400
Re: Check for military time gordonb.90ylr@burditt.org (Gordon Burditt) - 2015-10-22 18:21 -0500
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-10-22 20:23 -0400
Re: Check for military time gordonb.c5zx1@burditt.org (Gordon Burditt) - 2015-10-22 17:40 -0500
Re: Check for military time Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-10-22 11:12 +0200
Re: Check for military time Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-10-22 11:06 -0400
Re: Check for military time Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-10-22 17:18 +0200
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-10-22 13:17 -0400
Re: Check for military time Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-10-21 13:55 +0200
Re: Check for military time "M. Strobel" <strobel@example.com> - 2015-10-21 20:56 +0200
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-10-21 16:48 -0400
Re: Check for military time Stephan Elinghaus <221015.6.seli@spamgourmet.com> - 2015-10-22 13:16 +0200
Re: Check for military time Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-10-22 15:11 +0200
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-10-22 10:23 -0400
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-10-27 14:10 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-10-27 09:25 -0400
Re: Check for military time Jørn Andersen <jorn@jorna.dk> - 2015-10-27 15:19 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-10-27 10:41 -0400
Re: Check for military time Matthew Carter <m@ahungry.com> - 2015-10-27 23:03 -0400
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-10-27 23:29 -0400
Re: Check for military time Erwin Moller <erwinmollerusenet@xs4all.nl> - 2015-10-29 10:08 +0100
Re: Check for military time Matthew Carter <m@ahungry.com> - 2015-10-29 21:44 -0400
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-10-29 22:35 -0400
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-10-30 20:08 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-10-30 16:22 -0400
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-11-01 11:58 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-01 08:27 -0500
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-11-01 14:36 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-01 09:05 -0500
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-11-01 16:51 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-01 11:09 -0500
Re: Check for military time Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-10-30 22:33 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-10-30 20:01 -0400
Re: Check for military time Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-11-03 19:51 +0100
Re: Check for military time Erwin Moller <erwinmollerusenet@xs4all.nl> - 2015-11-02 13:51 +0100
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-11-02 18:57 +0100
Re: Check for military time Erwin Moller <erwinmollerusenet@xs4all.nl> - 2015-11-04 15:18 +0100
Re: Check for military time Matthew Carter <m@ahungry.com> - 2015-11-04 21:18 -0500
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-11-05 07:51 +0100
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-10-30 20:04 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-10-30 16:24 -0400
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-11-01 12:06 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-01 08:30 -0500
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-11-01 14:39 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-01 09:07 -0500
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-11-01 16:58 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-01 11:05 -0500
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-11-02 08:14 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-02 10:01 -0500
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-11-02 17:54 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-02 12:50 -0500
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-11-02 19:05 +0100
Re: Check for military time Tim Streater <timstreater@greenbee.net> - 2015-11-02 18:23 +0000
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-02 15:23 -0500
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-02 15:16 -0500
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-11-03 05:47 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-03 08:47 -0500
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-11-04 03:55 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-03 22:09 -0500
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-11-04 08:49 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-04 08:29 -0500
Re: Check for military time Paul Herber <paul@pherber.com> - 2015-11-04 14:14 +0000
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-04 10:00 -0500
Re: Check for military time Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-11-06 13:11 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-06 09:45 -0500
Re: Check for military time Matthew Carter <m@ahungry.com> - 2015-11-07 21:50 -0500
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-07 22:05 -0500
Re: Check for military time gordonb.2zzss@burditt.org (Gordon Burditt) - 2015-11-08 20:50 -0600
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-11-09 10:29 +0100
Re: Check for military time gordonb.00syf@burditt.org (Gordon Burditt) - 2015-11-10 23:42 -0600
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-11-11 07:46 +0100
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-11-11 07:50 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-11 08:06 -0500
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-11-11 15:15 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-11 09:21 -0500
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-11-11 17:46 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-11 15:12 -0500
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-11-11 22:23 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-11 17:17 -0500
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-11 08:05 -0500
OT: Munging addresses (was: Re: Check for military time) Arno Welzel <usenet@arnowelzel.de> - 2015-11-11 19:18 +0100
Re: OT: Munging addresses Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-11 15:16 -0500
Re: OT: Munging addresses Arno Welzel <usenet@arnowelzel.de> - 2015-11-11 22:29 +0100
Re: OT: Munging addresses Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-11 17:20 -0500
Re: OT: Munging addresses Arno Welzel <usenet@arnowelzel.de> - 2015-11-12 07:47 +0100
Re: OT: Munging addresses Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-12 10:15 -0500
Re: OT: Munging addresses Arno Welzel <usenet@arnowelzel.de> - 2015-11-12 17:17 +0100
Re: OT: Munging addresses Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-12 11:59 -0500
Re: OT: Munging addresses Arno Welzel <usenet@arnowelzel.de> - 2015-11-12 18:51 +0100
Re: OT: Munging addresses Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-12 14:20 -0500
Re: OT: Munging addresses Arno Welzel <usenet@arnowelzel.de> - 2015-11-12 20:59 +0100
Re: OT: Munging addresses Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-12 16:54 -0500
Re: OT: Munging addresses Jim Higgins <ILikeMy@Privacy.invalid> - 2015-11-18 16:24 +0000
PHP code section end marker (was: Check for military time) Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-10-27 22:58 +0100
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-10-30 20:01 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-10-30 16:27 -0400
Re: Check for military time Arno Welzel <usenet@arnowelzel.de> - 2015-11-01 12:12 +0100
Re: Check for military time Jerry Stuckle <jstucklex@attglobal.net> - 2015-11-01 08:31 -0500
Page 7 of 7 — ← Prev page 1 2 3 4 5 6 [7]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2015-11-12 20:59 +0100 |
| Subject | Re: OT: Munging addresses |
| Message-ID | <5644EFAA.6000709@arnowelzel.de> |
| In reply to | #15882 |
Jerry Stuckle schrieb am 2015-11-12 um 20:20: > On 11/12/2015 12:51 PM, Arno Welzel wrote: >> Jerry Stuckle schrieb am 2015-11-12 um 17:59: >> >>> On 11/12/2015 11:17 AM, Arno Welzel wrote: >>>> Am 2015-11-12 um 16:15 schrieb Jerry Stuckle: >>>> >>>>> Oh, I understand it, all right. Like all trolls, you make claims then >>>>> try to deny ever making them when challenged to back up those claims. >>>> >>>> READ (<5643866B.60300@arnowelzel.de>): >>>> >>>> "Even worse - it may be the mailbox by someone *else*." >>>> >>>> You understand the part "may be"? Do you? I don't think so. >>>> >>>> >>> >>> I understand it, all right. And I understand you once again are still >>> trying to weasel out of your words, because you can't back up your >>> claims when challenged. >> >> I am not challenged. It seems a challenge for you to understand your own >> mother language. >> >> > > Nope. I understand English perfect. And I understand YOU perfectly. I don't think so. Or why do you believe that "may be" means "Jerry Stuckle uses someone elses mailbox"? -- Arno Welzel http://arnowelzel.de http://de-rec-fahrrad.de http://fahrradzukunft.de
[toc] | [prev] | [next] | [standalone]
| From | Jerry Stuckle <jstucklex@attglobal.net> |
|---|---|
| Date | 2015-11-12 16:54 -0500 |
| Subject | Re: OT: Munging addresses |
| Message-ID | <n231lm$pcg$1@dont-email.me> |
| In reply to | #15883 |
On 11/12/2015 2:59 PM, Arno Welzel wrote: > Jerry Stuckle schrieb am 2015-11-12 um 20:20: >> On 11/12/2015 12:51 PM, Arno Welzel wrote: >>> Jerry Stuckle schrieb am 2015-11-12 um 17:59: >>> >>>> On 11/12/2015 11:17 AM, Arno Welzel wrote: >>>>> Am 2015-11-12 um 16:15 schrieb Jerry Stuckle: >>>>> >>>>>> Oh, I understand it, all right. Like all trolls, you make claims then >>>>>> try to deny ever making them when challenged to back up those claims. >>>>> >>>>> READ (<5643866B.60300@arnowelzel.de>): >>>>> >>>>> "Even worse - it may be the mailbox by someone *else*." >>>>> >>>>> You understand the part "may be"? Do you? I don't think so. >>>>> >>>>> >>>> >>>> I understand it, all right. And I understand you once again are still >>>> trying to weasel out of your words, because you can't back up your >>>> claims when challenged. >>> >>> I am not challenged. It seems a challenge for you to understand your own >>> mother language. >>> >>> >> >> Nope. I understand English perfect. And I understand YOU perfectly. > > I don't think so. Or why do you believe that "may be" means "Jerry > Stuckle uses someone elses mailbox"? > > Oh, yes, I understand you perfectly. But it's obvious YOU don't understand English as well as you think. Typical for a troll. Keep trying to deny it. You're just making a bigger fool of yourself. -- ================== Remove the "x" from my email address Jerry Stuckle jstucklex@attglobal.net ==================
[toc] | [prev] | [next] | [standalone]
| From | Jim Higgins <ILikeMy@Privacy.invalid> |
|---|---|
| Date | 2015-11-18 16:24 +0000 |
| Subject | Re: OT: Munging addresses |
| Message-ID | <bi4p4bh1b04dccegc58ncnue0jptu91047@4ax.com> |
| In reply to | #15874 |
On Wed, 11 Nov 2015 22:29:28 +0100, in <5643B338.1010301@arnowelzel.de>, Arno Welzel <usenet@arnowelzel.de> wrote: >Jerry Stuckle schrieb am 2015-11-11 um 21:16: > >> On 11/11/2015 1:18 PM, Arno Welzel wrote: >>> Jerry Stuckle schrieb am 2015-11-11 um 14:05: >>> >>>> On 11/11/2015 1:46 AM, Arno Welzel wrote: >>> [...] >>>>> It's even more rude to use munged addresses. >>>>> >>>>> See: >>>>> >>>>> <http://www.interhack.net/pubs/munging-harmful/> One man's seriously outdated view... consisting largely of the concept of "we all need to take one for the team." Nonsense! Rather than stand up to be shot, my approach is to make my publicly revealed email address useless to spammers because otherwise spammers will make email useless to me as a means of personal communication. The "take one for the team" approach assumes that if we all stand up in the line of fire and complain when we're shot, the complaints will eventually stop the spam. That nonsensical approach to fighting spam died in the mid-90s. >>>>> <https://en.wikipedia.org/wiki/Address_munging> Article is VERY SERIOUSLY outdated in both time and viewpoint. It refers to RFC 1036, which was rendered obsolete 6 years ago. It was replaced by RFC 5536 and 5537, neither of which address the validity of the From: address... only it's format. It also advocates the use of personally maintained email filters. This is an absolutely ludicrous solution to spam given the myriad of spoofed From: addresses typical spammers use. Filtration on the From: field is a ludicrous suggestion considering it's trivially forgeable. >>>>> <https://woozle.org/~neale/papers/reply-to-still-harmful.html> The author's writing style made reading this almost mind numbing. In the end, the standard he dissects - RFC2822 - refers to email, not Usenet articles. And he's talking about the Reply-to: field, not the From: field. I don't see any Reply-to: field in Jerry's articles. >>>> Bullshit. My munging my email address does not harm you or anyone else. >>> >>> It does. And the reasons are explained above. I think you need to speak for yourself rather than refer to a bunch of seriously outdated articles that upon careful reading have very little relevance to this discussion. >> You tell me just HOW my munging my email address is hurting you. Don't >> point at someone else's opinion (which is full of crap, anyway). Tell >> me why it is harming YOU. > >When I hit "reply", the mail will not be delivered, since you don't put >a valid address to the From: header. > >You may not see this "hurting" anyone - but in fact this is a sabotage >of a working system where one can just reply someone using the provided >functions in their software. You force people to invest more time as >neccessary to fix a broken e-mail-address according to your instructions >just because you want to avoid spam. Arno! Your argument above fails completely unless we accept the notion that you have an inherent right to have your email delivered to anyone you send it to. You have no such right. It doesn't take a lot of thought on that to realize it's really nothing more than the same twisted right of "free speach" that's claimed by spammers. You have no right to convenience when it comes to sending email to someone. If I choose to require you to solve a 4th order polynomial equation to determine how to modify my email address to make it deliverable, then you either go thru that exercise or it's pointless for you to click SEND... or you can, by error or choice, be situationally unaware that you need to remove a character from an email address to make it deliverable. You have a right to blindly click REPLY, pound out a message, blindly click SEND, and then you have a right to suffer the consequences of your actions by later receiving your message back marked undeliverable. You have a number of options, but none of them includes a right to convenient deliverability. In the environment we operate there can be no right to convenience of this sort. Why? Because your convenience is all too easily my inconvenience. I don't want replies to Usenet postings via email. More importantly, I don't want my email address snarfed off of Usenet by spammers and put onto a "Million Addresses" CD that will be sold to gullible new spammers and result in my wanted email being lost among all the spam in my inbox. Been there, done that, learned from my mistake. You need to learn from your mistake... that being that you need to pay attention to directions given to make an email address deliverable before you click SEND... because the inconvenience you suffer if you don't doesn't trump the inconvenience I experience if I don't munge my email address.
[toc] | [prev] | [next] | [standalone]
| From | Thomas 'PointedEars' Lahn <PointedEars@web.de> |
|---|---|
| Date | 2015-10-27 22:58 +0100 |
| Subject | PHP code section end marker (was: Check for military time) |
| Message-ID | <4576743.C76ZohRfH3@PointedEars.de> |
| In reply to | #15797 |
J�rn Andersen wrote: ^^^^ The characters in your From header are not properly encoded, so they end up as garbage with readers unless their newsreaders make a good guess. The same may be true of Subject header field values posted by you, which can effectively destroy threads you participate in (depending on the previous Subject, if any, and your choice of characters if it is an OP). Please either do not post non-ASCII-characters there, use a server that can fix this on the fly, or try upgrading Forté Agent (the current version is 8.0, you are using 6.0.x). > […] Jerry Stuckle […] wrote: >> On 10/27/2015 9:10 AM, Arno Welzel wrote: > <snip> >>> JFTR: PHP scripts can not only output text and additional white space at >>> the end may invalidate the output. Omitting the closing tag does not >>> cause any harm but will avoid this for sure. >> Good programming will avoid this problem, for sure. Crappy programmers >> need crappy workarounds. > > php.net recommends not using the PHP closing tag if a file is pure > PHP code. > http://php.net/manual/en/language.basic-syntax.phptags.php So do the PEAR Coding Standards since quite a while, and more recently PSR-2 which have been developed and are observed by major (PHP) players such as CakePHP, Composer, Contao, Doctrine, Drupal, Joomla, PEAR, phpBB, phpDocumentor, SugarCRM, Symfony, and Zend Framework 2. (AISB. But Jerry Stuckle is always right. You will be hated. Resistance is futile :->) <http://www.php-fig.org/psr/psr-2/> <http://www.php-fig.org/members/> But in fact, it is best to *never* write the “?>” at the *end* of a file that is parsed by PHP because where there is not only pure PHP code (like in a template) you *also* do not want to output whitespace content accidentally. (And this can happen easily. For example, unless you tell it not to, Vim always appends newline on save.) An end marker there is quite simply an *unnecessary* cause of problems, and nothing is gained by writing it. PHP parsing will end automatically anyway when EOF is reached, and any standalone whitespace is ignored in parse mode. -- PointedEars Zend Certified PHP Engineer Twitter: @PointedEars2 Please do not cc me. / Bitte keine Kopien per E-Mail.
[toc] | [prev] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2015-10-30 20:01 +0100 |
| Message-ID | <5633BE73.50909@arnowelzel.de> |
| In reply to | #15796 |
Jerry Stuckle schrieb am 2015-10-27 um 14:25: > On 10/27/2015 9:10 AM, Arno Welzel wrote: >> Jerry Stuckle schrieb am 2015-10-22 um 16:23: >> >>> On 10/22/2015 9:11 AM, Thomas 'PointedEars' Lahn wrote: >> [...] >>>> Avoid ending PHP files with that; you may be accidentally outputting >>>> trailing whitespace otherwise. >>>> >>> >>> Another stoopid comment by the troll. >> >> JFTR: PHP scripts can not only output text and additional white space at >> the end may invalidate the output. Omitting the closing tag does not >> cause any harm but will avoid this for sure. >> >> > > Good programming will avoid this problem, for sure. Crappy programmers > need crappy workarounds. It's not a "crappy workaround". If PHP would *require* a closing tag at the end of a script it would cause a runtime error when omitting it. But it does not - for good reasons. Maybe you believe the official PHP documentation more than me: <http://php.net/manual/en/language.basic-syntax.phptags.php> Cite: "If a file is pure PHP code, it is preferable to omit the PHP closing tag at the end of the file. This prevents accidental whitespace or new lines being added after the PHP closing tag, which may cause unwanted effects because PHP will start output buffering when there is no intention from the programmer to send any output at that point in the script." > Omitting a closing tag will cause harm if someone tries to add html at > the end of the page. Well - when changing a script one should do this carefully anyway and not just add HTML without looking at the code. Or do you just blindly add HTML to production code and use it without testing? -- Arno Welzel http://arnowelzel.de http://de-rec-fahrrad.de http://fahrradzukunft.de
[toc] | [prev] | [next] | [standalone]
| From | Jerry Stuckle <jstucklex@attglobal.net> |
|---|---|
| Date | 2015-10-30 16:27 -0400 |
| Message-ID | <n10jm0$s68$1@dont-email.me> |
| In reply to | #15812 |
On 10/30/2015 3:01 PM, Arno Welzel wrote: > Jerry Stuckle schrieb am 2015-10-27 um 14:25: > >> On 10/27/2015 9:10 AM, Arno Welzel wrote: >>> Jerry Stuckle schrieb am 2015-10-22 um 16:23: >>> >>>> On 10/22/2015 9:11 AM, Thomas 'PointedEars' Lahn wrote: >>> [...] >>>>> Avoid ending PHP files with that; you may be accidentally outputting >>>>> trailing whitespace otherwise. >>>>> >>>> >>>> Another stoopid comment by the troll. >>> >>> JFTR: PHP scripts can not only output text and additional white space at >>> the end may invalidate the output. Omitting the closing tag does not >>> cause any harm but will avoid this for sure. >>> >>> >> >> Good programming will avoid this problem, for sure. Crappy programmers >> need crappy workarounds. > > It's not a "crappy workaround". > > If PHP would *require* a closing tag at the end of a script it would > cause a runtime error when omitting it. But it does not - for good reasons. > > Maybe you believe the official PHP documentation more than me: > > <http://php.net/manual/en/language.basic-syntax.phptags.php> > > Cite: > > "If a file is pure PHP code, it is preferable to omit the PHP closing > tag at the end of the file. This prevents accidental whitespace or new > lines being added after the PHP closing tag, which may cause unwanted > effects because PHP will start output buffering when there is no > intention from the programmer to send any output at that point in the > script." > As I said - I don't think much of the "programmers" at PHP. I haven't seen a lot of competence from most of them, and have seen a fair amount of incompetence from several. >> Omitting a closing tag will cause harm if someone tries to add html at >> the end of the page. > > Well - when changing a script one should do this carefully anyway and > not just add HTML without looking at the code. Or do you just blindly > add HTML to production code and use it without testing? > > Trolls being careful? ROFLMAO! But we know you only exist to raise hell on usenet. You don't do any real programming. Time for you to go back to washing dishes, Arno. -- ================== Remove the "x" from my email address Jerry Stuckle jstucklex@attglobal.net ==================
[toc] | [prev] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2015-11-01 12:12 +0100 |
| Message-ID | <5635F38D.5090603@arnowelzel.de> |
| In reply to | #15817 |
Jerry Stuckle schrieb am 2015-10-30 um 21:27: > On 10/30/2015 3:01 PM, Arno Welzel wrote: [...] >> Well - when changing a script one should do this carefully anyway and >> not just add HTML without looking at the code. Or do you just blindly >> add HTML to production code and use it without testing? >> >> > > Trolls being careful? ROFLMAO! But we know you only exist to raise > hell on usenet. You don't do any real programming. So far it seems you are the only troll here. You don't want to discuss about things, you just want to insult people - and of course you would never stop as long as you don't have the last word. -- Arno Welzel http://arnowelzel.de http://de-rec-fahrrad.de http://fahrradzukunft.de
[toc] | [prev] | [next] | [standalone]
| From | Jerry Stuckle <jstucklex@attglobal.net> |
|---|---|
| Date | 2015-11-01 08:31 -0500 |
| Message-ID | <n15432$6kb$3@dont-email.me> |
| In reply to | #15822 |
On 11/1/2015 6:12 AM, Arno Welzel wrote: > Jerry Stuckle schrieb am 2015-10-30 um 21:27: > >> On 10/30/2015 3:01 PM, Arno Welzel wrote: > [...] >>> Well - when changing a script one should do this carefully anyway and >>> not just add HTML without looking at the code. Or do you just blindly >>> add HTML to production code and use it without testing? >>> >>> >> >> Trolls being careful? ROFLMAO! But we know you only exist to raise >> hell on usenet. You don't do any real programming. > > So far it seems you are the only troll here. You don't want to discuss > about things, you just want to insult people - and of course you would > never stop as long as you don't have the last word. > > Nope, you're the troll - as you've proven time and time again. But then trolls always try to blame someone else for their shortcomings - as you've again shown in this thread. -- ================== Remove the "x" from my email address Jerry Stuckle jstucklex@attglobal.net ==================
[toc] | [prev] | [standalone]
Page 7 of 7 — ← Prev page 1 2 3 4 5 6 [7]
Back to top | Article view | comp.lang.php
csiph-web