Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Jolly Roger Newsgroups: comp.sys.mac.system Subject: Re: Latest IOS/OS X SSL security flaw Date: 24 Feb 2014 23:17:43 GMT Organization: People for the Ethical Treatment of Pirates Lines: 43 Message-ID: References: <220220141415089899%nospam@nospam.invalid> <2NWdnQXy6oxRY5XOnZ2dnUVZ_qSdnZ2d@giganews.com> X-Trace: individual.net rbfagFHUQrIDBWS1s/pwpAgq6tJwNk/jY5gfc+6Lcp2gHBHLEy Cancel-Lock: sha1:z0cYsAzDKIof7mTJqKym1tL/j3s= X-Face: _.g>n!a$f3/H3jA]>9pN55*5<`}Tud57>1Y%b|b-Y~()~\t,LZ3e up1/bO{=-) User-Agent: slrn/1.0.1 (Darwin) Xref: csiph.com comp.sys.mac.system:57020 On 2014-02-24, Alan Browne wrote: > On 2014.02.24, 00:04 , Jolly Roger wrote: >> On 2014-02-24, Lewis wrote: >>> In message >>> Alan Browne wrote: >>>> if bar(foo) then >>>> begin >>>> brat (tat); >>>> stat (a,v) >>>> end >>>> else >>>> faggetaboutit("I object!"); >>> >>> Is how I would space that. However, that else is something I >>> particularly dislike. That, to me, is terrible obtuse code. >>> >>> if bar(foo) { >>> brat(tat); >>> stat(a,v); >>> } else { >>> faggetaboutit("I object!"); >>> } >>> >>> That is much clearer and more concise that the code above. >>> >>> I don't like putting {'s on empty lines for no reason, but the last >>> close bracket matches up the else and if showing the block has ended. >>> >>> That said, I can't stand writing in python because of its reliance of >>> using white space for block control. That seems like the stupidest idea >>> any language designer ever had. >> >> White space isn't the enemy. Far from it. > > As structure guidance for the compiler it sure is ... Most compilers are designed to ignore white space. Hardly an enemy! -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR