yuubi

This readline behavior follows a Unix tty driver. I'm not sure off the top of my head which one introduced it. I don't think it was on xenix but am pretty sure some 4.x bsd had it.

If you mainly care about time and can tolerate a few microseconds of error, usually being able to see 4 satellites might well be enough.

I remember seeing a gps receiver designed just for time that could maintain sync using only one satellite (it assumed that it was bolted to an immovable object, and it might have needed to see 4 satellites at once at some point).

Maybe it's UB only because implementation-specified is too onerous and it didn't seem to be worth defining a bounded "unpredictable result" behavior.

Given the standard, it's obvious why i=i++ is undefined: it modifies i twice between sequence points. The question is why it was "undefined" (in which the implementation is allowed to make demons fly out your nose) and not something like, say, the "unpredictable" that occurs in many architecture specs (in which the program behaves as if i had been set to something in particular, but with no requirement on which value it is: unchanged is ok, incremented is ok, 12345 is ok if i is wide enough to hold it, but silently failing to generate any code for statements that occur after the i=i++ isn't).

The lower powers 10–1000 take a prefix of 2–9 to multiply them, and omitting the prefix means one.

1 ichi

2 ni

10 juu (not ichi juu)

20 ni juu, literally two ten

100 hyaku

200 ni hyaku

The powers of 10000 seem to take an obligatory prefix 1–9999, formed the usual way (I've never heard just "man" for 10k, always "ichi man", and 12340000 would be literally translated to "thousand two hundred three ten four ten-thousand", while none of the smaller powers seem to ever take a prefix > 9.)

The above is based on not living in Japan, though, so the sample of numbers I've seen might well be missing some things that occur in actual native speech by someone not teaching a first-year class.

Often people who are leaving will either have their assets moved somewhere they'll certainly have access to later or just liquidate (generally on better than firesale terms).

Citadels (like the keepstar that changed hands) work differently: you can get everything in a citadel moved to the nearest suitable npc station at the cost of 15% of its value and a 20-day wait, worst case (google "eve asset safety" for the full details).

I thought the glass process was basically melting sand and adding some trace additives, rather than forcing any chemical reactions uphill. Recycled glass also needs melted (if it doesn't, that's called a reusable bottle, not recycling).

Maybe because in ASCII-63 the _ codepoint meant left-arrow (which was preserved in at least smalltalk systems much past the 60s)?

An example usage: http://www.commondraft.org/#ConfKExpress

(I'm not sure how the reference is meant to work because I'm pretty sure commondraft.org has been edited since I saw it some years ago; maybe it's meant to copy whole sections and then include the specific details in a page like the one linked above?)

Note that the CC license mentioned in the header isn't actually useful except to lawyers: it contains the noncommercial restriction with separate special permission for most uses by licensed attorneys (looks intended to prevent non-attorneys from actually using anything there in transactions).

---

3GPP2 C.S0002-A section 1.3 "CDMA System Time":

All base station digital transmissions are referenced to a common CDMA system-wide time scale that uses the Global Positioning System (GPS) time scale, which is traceable to, and synchronous with, Universal Coordinated Time (UTC). GPS and UTC differ by an integer number of seconds, specifically the number of leap second corrections added to UTC since January 6, 1980. The start of CDMA System Time is January 6, 1980 00:00:00 UTC, which coincides with the start of GPS time.

System Time keeps track of leap second corrections to UTC but does not use these corrections for physical adjustments to the System Time clocks.

---

I'm pretty sure the only use of leap seconds in CDMA is for converting system time to customary local time, along with the daylight-time indicator and time-zone offset also contained in the sync channel message.

Edit: C.S0005-E section 2.6.1.3 says the mobile station shall store most of the fields of the sync channel message; it may store leap second count, local time offset, and daylight time indicator. This suggests that these fields aren't really that important for talking CDMA.

Used "Terro Ant Killer II", which is syrup that contains borax and works about as well as the original formula that contained arsenic.

Reminds me of the ancient story of the electronics manufacturer that sourced some resistors or whatever from Japan for the first time. The spec called for max 1% bad parts or whatever. When the parts arrived, the box contained a packet with a note that said something like "Thanks for your order. We are unsure why you want 1% defective parts, but for your convenience, we have packaged them separately."

    ftp ftp.netscape.com

The safe thing is to use wire from a vendor that rates it honestly to conservatively, and start within the ratings.