The sound triangulated was in cryogenic liquid oxygen at 50 PSI. The speed of sound in that is approximately 1 kilometer per second.This paper is about calculating the exact speed. Elon talked in the conference about reading telemetry with millisecond accuracy. But this would yield only 1 meter resolution.

That ought to be easy to test, at least experimentally, using capsense...

That's not the way it works. When cross-compiling, configure runs on the host. It tests that things compile. It doesn't test that they run.

Roger,

This is great. It does look like a 1:1 mapping to what we expect autoconf to do, except neater and maintainable.

The only problem with selling this to GNU folks is that it would make CMake a prerequisite to everything. But I think it's worth it. And then there's inertia. And the language isn't as pretty as we'd like.

Can you see any other possible objections?

Thanks

Bruce

the Emacs vs VI war is over (Emacs won)

Nope. B-)

When I got my first UNIX box, back in the '80s, it had two megabytes and did NOT have demand paging, which would have allowe a larger virtual image to run. That was too small to compile emacs. (The joke at the time was that the name was really an acronym for Eight Megabytes And Constantly Swapping. B-) )

So I learned VI. Then I used it VERY heavily for years, on the original conferencing system whose software was later ported to The Well. After that a number of editing idioms were "wired into" my hindbrain and I could do the things I wanted to do with text very efficiently with vi.

As machines improved I tried emacs several times. Each time I found that the stuff I depended on took about 1.5 to 3 times as many keystrokes. This was too much of a penalty to pay for the handful of features it offered.

At one point I considered going to it but running in a vi emulator mode and gradually migrating to native idioms. But I discovered that, kitchen sink that it was, it had TWO vi emulator modes, each with distinct deviations from vi (alias "bug sets"). With one vi emulator, even with substantial shortcomings, I might still have made the shift. With two there was no easy way to chose, so I didn't bother.

Now I'm using vim, which is close enough. One of my regular colleagues is an emaxian rather than a vithian and we get along just fine. B-)

Also: It's not clear to me which group should be handling this. It seems to be a conflict between how two projects downstream of the compiler itself are handling a global namespace.

I'd only expect the compiler guys to fix it if they decided the downstream stuff was a problem and pulled part of it into their own stuff to settle the matter.

Wouldn't it be easier to check your bugzilla ticket?

There were already several tickets out on it (and flames from the maintainers about duplicates) so I didn't file another. None of them seemed to indicate that anyone, let alone the core compiler crew, were intending to do anything abut it.

I was hoping someone more actively engaged in either reporting or dealing with the issue might happen to be participating here and care to chime in. B-)

Meanwhile, others should know that there IS (or, we can hope, WAS) an issue before they make plans to try to use the toolset for a new project.

Must of been a big hit to the ego to find your spouse's profile on the cheating site you worked at; then to add insult to injury you get laid off because your spouse was a member and you can't even confront them because of the NDA you signed!

These people must be pretty stupid to give out any personally traceable data anyway, that's what "magic jacks", burner phones and "Green Dor" cards are for.