these places don't hire people who don't understand floating point numbers. see d.e. shaw group, renaissance technologies.
S
sheriffpony
@sheriffpony
0
Reputation
3
Posts
27
Profile views
0
Followers
0
Following
Best posts made by sheriffpony
This user hasn't posted anything yet.
Latest posts made by sheriffpony
-
RE: WTF Job Listing
-
I'm lovin' it
Just sharing the joy of all these great OPPORTUNITIES Caltech opens for you.
-
RE: Gotos considered harmful, but break considered OK?
it may look awkward, but it's a pretty standard construct. deal. its benefit over a goto is that it can be used several times in the same scope without having to readjust the labels and is copy/paste-safe.
as for exceptions, they are a lot more expensive with stack unwinding and looking for handlers and what-not (though I'll agree that unless the code's in a tight loop, it's not much of an argument anymore). but really, using exceptions for regular error handling is a faux pas.
obvious variations on the theme:
do { [...] if(_tfopen_s(&fo, moo, _T("wbT")) != 0) { SetLastError(cantAccessTempDir); break; } [...] } while(false);
or something that I've seen crop up in win32 code:
ok = ok && NULL != (dc = GetDC(NULL)); ok = ok && NULL != (hdib = (HBITMAP)LoadImage(0, name, IMAGE_BITMAP, 0, 0, LR_CREATEDIBSECTION | LR_LOADFROMFILE));
BITMAPINFO bi = {0}; BITMAPINFOHEADER &bih = bi.bmiHeader; bih.biSize = sizeof(bih); ok = ok && 0 != GetDIBits(dc, hdib, 0, 0, NULL, &bi, DIB_RGB_COLORS); if(ok) { [...] } // do this scope's releases</pre><p>looks weird if you've never seen it before, but it's also pretty standard (`ok` can be an HRESULT in code that works with COM, etc.).</p>