Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Arno Welzel Newsgroups: comp.lang.php Subject: Re: Check for military time Date: Thu, 5 Nov 2015 07:51:41 +0100 Lines: 87 Message-ID: <563AFC7D.3070004@arnowelzel.de> References: <1874827.QbCUPLQBcH@PointedEars.de> <562F77B7.1050001@arnowelzel.de> <8737wvd78w.fsf@ahungry.com> <5631e20e$0$23743$e4fe514c@news.xs4all.nl> <87y4elb05f.fsf@ahungry.com> <56375c5b$0$23788$e4fe514c@news.xs4all.nl> <5637A403.5030200@arnowelzel.de> <563a13ba$0$23779$e4fe514c@news.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Trace: individual.net JNAi19omiM/DV0rrqCRjdQVR45qaGSCNdXxxpwHMmCONWi1UFJ Cancel-Lock: sha1:ywFtzGS1G1Xzillgns4IIc5BgR0= In-Reply-To: <563a13ba$0$23779$e4fe514c@news.xs4all.nl> Xref: csiph.com comp.lang.php:15855 Erwin Moller schrieb am 2015-11-04 um 15:18: > On 11/2/2015 6:57 PM, Arno Welzel wrote: > > Erwin Moller schrieb am 2015-11-02 um 13:51: [...] > >> 2) Change the language, violate the logical assumption that each > >> opening tag should be accompanied by a closing tag. > >> > >> > >> It is beyond my understanding how anyone can opt for the second > >> option. > > > > You will do this, when you first had to spend hours in finding bugs > > in a system which consist of hundreds of files and some problem shows > > up caused by unintentional whitespaces. > > No, that would not change my mind. > I know how hard it can be to find bugs, especially on a huge codebase. > I feel your pain. > But cure is worse than the pain. No - the cure is an official recommendation, as already mentioned several times: > The reason I make such a fuzz about this is this: > Where does this kind of "improvements" end? It is not an "improvement" - it's just part of the language PHP and totally valid. > Do you think it is acceptable if all calls to a method or function that > cannot be found will be replaced (by the language) by the one that > closely resembles the spelling used in the code because sometimes people > mistype the name of the function, or are confused by camelCase/CamelCase? No. And you start to mix up things which have nothing to do with each other. > Do you think it is acceptable if programmers leave out the closing curly > bracket in conditional statement, because they "forget sometimes" to > close it, and you have spend hours finding the problem? No. And this also has nothing to do with the topic. And as you introduced it - that's my response for this ;-) > Really, sometimes you just have to draw a line, and demand a certain > mastery of the job. If people cannot deliver, they should go elsewhere. I don't think this applies here. > >> What is even more flabberghasting is the fact many people are willing to > >> defend that crazy decision. > > > > As already mentioned by T. Lahn: > > > > > > > > Cite: > > > > "The closing ?> tag MUST be omitted from files containing only PHP." > > > > I choose to respond with: > > https://yourlogicalfallacyis.com/appeal-to-authority Wrong. I explained why I believe that it makes sense to omit closing tags in PHP scripts to avoid an unintentional whitespace without - and my argument was NOT that one should do just it, because some authority says to do so! But since some people say that omitting a closing tag at the end of a PHP script is just a dirty workaround I referred to and to show that *others* recommend this as well - including the staff of PHP itself. -- Arno Welzel http://arnowelzel.de http://de-rec-fahrrad.de http://fahrradzukunft.de