Ryan McGuire wrote:In general, "You bet," means, "I will do exactly as you requested."
Linwood Hayes wrote:Last week, we planned a picnic with a few friends and families. I offered a ride/carpool to a friend saying "We can drive and if you want to go with us, let me know." Then I realized he was little hesitating, so I added "If you have other plan, feel free to go ahead with your plan..". He said "You bet." Can somebody tell me what does "you bet" mean here ? Does it mean he did have other plans or what ? You may ask why I didn't ask himself what it meant that time. Be honest, I just didn't want to make myself look dumb by letting people feel I couldn't grasp English..
Carey Brown wrote:You are comparing the references to "ab" and "ab " (note the extra space).
The '+' operator has a higher precedence than the '==' operator.
Obviously the while loop should stop when the returned node is none?
Piet Souris wrote:hi DJ,
long time no see! You seem to be very busy, but that is a good thing.
I had to read that assignment twice, but I think I got it. You are given N cities (vertices) and M lines of input indicating where a pilot can fly to and from (edges). So, it is an undirected Graph with N vertices and M edges. And the question is what the shortest path is between any two cities. Correct me if I'm wrong. Now, first thing what comes to mind is Dijkstra's algorithm: Dijkstra.
So, have a read and see if you agree with me!
Stephan van Hulst wrote:If your method call can succeed or fail, there are two acceptable options:
Return a boolean value indicating success. This is appropriate if failure of the method call is a normal occurrence and can happen regularly. Throw an exception. This is almost always the more appropriate option, because failure is usually an exceptional situation.
Why would an SQL query fail, unless something exceptional happened? So throwing an exception is probably the way to go. Now, you have two ways of throwing the exception:
Paul Clapham wrote:Can you burp the alphabet?
Michael Angstadt wrote:As a software developer, it's important to make your code readable so that other developers (as well as your future self) can understand what you've written. However, complex regular expressions are notoriously difficult to read. Do you have any tips for improving the readability of regular expressions? Thank you!
Henry Wong wrote:
Ryan McGuire wrote:
Hee Hee. Only a fellow trainer would understand the significant of those numbers....
Too bad there are very little reasons to friend a trainer that you will never battle, raid, or trade with... or I would send an invite.