A reader offered the following comment, on a small technical article, here. I checked out his site and its pretty consistent. I choose to regard it as a cry for help, but that could be overgenerous. Count your blessings, friends. The power of youth and confusion are always around the corner… and yet, I neither wanted to just delete this or pass it along as sent, you know?
[Edited (###### added) by me]
Here’s the tide table for this coming weekend at Moss Beach, just north of Princeton By The Sea, at the north edge of Half Moon Bay. High tide, +6 feet, at Midnight between Friday and Saturday, 1:00am between Saturday and Sunday. Low, low, tides at 7:00am, -1.5 feet!! on Saturday, -1.25 feet, at 7:48am, Sunday.
So, by crackie, we’ll be there as early as we an on Sunday. Sunrise is before 6:00am, so no shortage of light. Do a web search and you’ll discover this place has the best tidepools that ever existed- perhaps 1/4 mile or more along the coast, as much as 200 yards off shore of the normal high tide mark. A huge shelf of very low quality rock, normally around or perhaps a bit below the 0 foot level, that will be a good foot above sea level on Sunday Morning.
June 13, 2014 in Exhibits, Me, Nature, Parks, Photos, Recomended, San Francisco Bay Area, Science Fair Projects, Uncategorized, Where
Tagged Father's Day, low, Moss Beach, tide
for fname in os.listdir(os.getcwd()):
print “text.count( hi mom )”
print text.count(‘hi mom’)
Posted in Mac OS-X, Macintosh Computers, Personal Computers, Programming Languages, Python, Software development
Tagged baby step, for, function call, import, print, program, Python, trivial
A philosophic reason to sets pointers to NULL after free’ing them.
On reflection, I think I got this one right, and I kinda like it! I have experienced other people’s double-free errors, surprisingly, but the value of crashing-on-access-via-null is persuasive to me. Making double-free happen silently and without error is a small cost for positively crashing on a rogue access through a freed pointer.
January 24, 2014 in Computers, Personal Computers
Tagged "C language", C++, computer programming, double-free, excluding bad, free, including good, malloc, memory, philosophy, philosophy of including good or excluding bad, pointers
Mid-production Hawker Hurricane, Mk I, with Rotol constant-speed prop and a Spitfire spinner (the dedicated Hurricane spinner arrived in late 1940). This is what one would look like if it was painted all together, and they stopped before applying the national and service markings. Just “B” pattern camouflage on top, Dark Green and Dark Earth. Starboard side white, port side black, underneath, meeting at the centerline. Nothing of the original “Aluminum” finish remains outside, but the wheel wells and inside of the undercarriage doors might well be “Aluminum”, still.
The “A” and “B” camouflage patterns were mirror images, so this starboard, “B” scheme, is the same as a port-side “A” scheme, except reversed left to right
The black/white underside recognition features was ordered in August 1938. While the requirement for black under the port wing was made known fairly readily, how to treat the starboard wing, horizontal stabilizers and fuselage underside was somewhat to very unclear between 8/38 and 4/39. The intent was to have the port side black up to the center of the fuselage, and the starboard side white, up to the center of the fuselage, as this drawing and its companion show.
Posted in Military, WWII
Tagged "B" pattern, "Dark Green", 1939-1940, black, Dark Earth, dH 2 pitch prop, ejector exhausts, Hawker, Hurricane, mid-production, Mk I, starboard profile, Temperate Earth scheme, white
Another mid-period Hurricane. Between Munich (August, 1938) and the invasion of Poland (September, 1939), the, still, “peacetime” RAF expanded dramatically and was flooded with new technology. While everyone more or less understood the written instructions to paint the underside of the port wing black, for recognition when airborne, what to do with the rest of the plane was not always grasped. Black and white across the undersurface of the wing, meeting at the center line, was a durable interpretation, frequently seen, with the rest left as built, in Aluminum finish. Here’s what that would look like with no national or service markings.
Note, the “B” scheme camouflage is the mirror image of the “A”, same blobs of color, but on the other side. So that a row of airplanes would not stand-out by looking identical.
(Click on image for all size access)
A mid-production Hurricane Mk I. “A” pattern camouflage. Underside finished in Aluminum but outer wing panels are black on port side and white on starboard. De Havilland 2 position prop (their build of the Ham.-Std patent), ejector exhausts, anti-spin strake and rudder extension. Port profile.
de Havilland’s metal prop and related hydraulics weighed 350lb more than the Watts wooden prop, but offered a fine (for acceleration from low speed) and coarse (for high speed) settings. With a takeoff speed under 100mph and a maximum speed above 300mph, the Hurricane with a fixed pitch prop was like an automobile with one gear from 20mph to 60. Unresponsive and twitchy at low speed, screaming like a banshee, unnecessarily, at top speed.
The camouflage pattern looked quite different from port side than from starboard, intended to disrupt the outlines of multiple planes parked on the ground. The “B” scheme was the mirror image of the “A” scheme, so that a line of planes parked in a single direction wouldn’t all look exactly the same.
At the beginning of the war, the “Dark Green” area was always painted Dark Green and the “Dark Earth” always painted Dark Earth, but in the later part of the war, colors were sometimes seen reversed, particularly if re-applied or revised in the field.
Posted in Uncategorized
Tagged "A" pattern, "Dark Green", aluminum, black, Dark Earth, dH 2 pitch prop, ejector exhausts, Hawker, Hurricane, mid-production, Mk I, port profile, Temperate Earth scheme, white