On Mar 3, 2014, at 11:59 AM, Chris Barker wrote:
> And significant indentation!
>
> really, no one beat me to that?
>
> ;-)
>
> There was a nice Blog post about this from a Google Chrome developer -- less
> critical than I'd think, who pointed out that it's really hard to write unit
> tests
And significant indentation!
really, no one beat me to that?
;-)
There was a nice Blog post about this from a Google Chrome developer --
less critical than I'd think, who pointed out that it's really hard to
write unit tests for this sort of thing, due to the need for a LOT
of scaffolding -- but
And, you know... unit tests to actually know if a the code would reject a
spoofed certificate?
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Todd Wrote in message:
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>
use modern programming languages with well designed exception handling
--
Android NewsGroup
On Mar 3, 2014 3:16 AM, "Charles R Harris"
wrote:
>
> This is from OS X 9
>
> if ((err = SSLHashSHA1.update(&hashCtx, &serverRandom)) != 0)
> goto fail;
> if ((err = SSLHashSHA1.update(&hashCtx, &signedParams)) != 0)
> goto fail;
> goto fail;
> if ((err = SSLHas
This is from OS X 9
if ((err = SSLHashSHA1.update(&hashCtx, &serverRandom)) != 0)
goto fail;
if ((err = SSLHashSHA1.update(&hashCtx, &signedParams)) != 0)
goto fail;
goto fail;
if ((err = SSLHashSHA1.final(&hashCtx, &hashOut)) != 0)
goto fail;
Heh, mayb
