Matthew Dennis wrote: ‘:’ ... AND, it's the '...' in other queries made at later dates ... (On a somber note: 64-bit Visual Studio launched but is not available in a standalone, one-time purchase, non-subscription license.)

Try designing stuff before going gung-ho with implementation on a unsupported technology / buzzword. GCS d--(d-) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++*      Weapons extension: ma- k++ F+2 X

True. I think it could be done near the end of the process assuming you're allowed to schedule outside of 8-5 and the candidate list either is all +-2 timezones or can be grouped into buckets like that. As far as willingness, a lot of engineers don't like the idea that our entire skillset is boiled down to whether we know the one trick for an optimal solution to a competitive programming question and yet we have to deal with that still. To be fair that's probably not everywhere but it does seem to be a growing trend.

I'm beginning to learn the same thing. The less you need, the more you have. Even a blind squirrel gets a nut...occasionally. JaxCoder.com

Interesting, but I have some doubts it is still relevant with modern compilers and CPUs. Even if it were, a simple lookup table would be faster for the purpose of finding the first estimation. This algortihm reminds me a bit of Bresenham's line algorithm - Wikipedia[^] : extremely clever, but once it was hard-wired in every graphcs chip there was little point knowing about it. Except maybe to apply such principles to similar problems in other areas. E. g. I tend to do calculations with 2D and 3D vectors a lot, and if I were to do these calculations straightforward, then yes, I'd need to do a lot of vector normalizations (i. e. calculations of 1/sqrt(x)). But in about 8-9 out of 10 cases I can avoid normalization alltogether by transforming the expressions. E. g. when I want to know whether a vector length is very small (effectively null), then I compare the squared length against the squared threshold value. Or when I calculate the intersection of a plane with a line, I determine the intersection without normalizing any vector. Instead I transform the equations in such a way that I end up with the squared length of the line direction vector, and the plane direction or normal vectors don't need to be normalized at all. I do agree that the explanations and specifically the animated number representations are formidable, though GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)

Yes, but specifically I'm talking about taking that state machine and turning it back into a regular expression. Real programmers use butterflies

Interesting problem... I've never looked into it because there was no such thing when I was programming for a living. It seems that the Keene's algorithm is key to the solution. This is something worth investigating, as I love state machines, and they seem to have gone out of favor. Will Rogers never met me.

Hi, i find Jonathan Allen's articles on InfoQ about new C# features very helpful: [^], [^]. Some of Steve Gordon's posts also: [^], and [^] «The mind is not a vessel to be filled but a fire to be kindled» Plutarch

Code bloat and Moore's Law? I thought that they already did! :confused: Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.

Sounds like a plan from Dr Evil!

Sometimes elements that appear to be common at first are not really common. Say for example, both forms have a name field. One might jump to the conclusion that the name field is common to both forms and factor it out for reuse. Then down the track one of the forms needs the name field to be changed to say nick name. Now we realise in hindsight that just because the code was identical between the forms in the first instance they were not really common code and more refactoring is now required. When you factor out common code try to make sure the cut is in areas that are unlikely to change if requirements change.

"Hey, Mary, that report was due an hour ago! What's up?" "#**^!!!" The Science of King David's Court | Object Oriented Programming with C++

So give him a title of Mr and this problem goes away. If you can't laugh at yourself - ask me and I will do it for you.

Kent Sharkey wrote: And I suspect that's by design. Of course... how else would they scam you that much $$$ setup your business online (while running theirs)? M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.

I am in the same situation as you. I would die of boredom first, before they throw me in debtor's prison. ;P It's hell getting old.

Completed my first print & wanted to let you know about filament usage. Filament usage is very small actually. Here is the sample filament they gave with the printer: https://i.stack.imgur.com/QukEv.png[^] There is a micro SD card in the center of that loop to give you an idea of how small amount this really is. Here is an item (chip clip) I printed with that filament (with much left over): https://i.stack.imgur.com/iWe65.png[^] I added a normal ball point pen for scale comparison. Here's what is left of the spool on the 3d printer (a lot): https://i.stack.imgur.com/Ae2BC.png[^] Hope this helps give you an idea.