|
amount is too small
Luc Pattyn
|
|
|
|
|
Indeed. I wonder if it wasn't, would the person who cashed it have been able to do so?  Imagine the fun mathematicians could have. 
"Marge, don't discourage the boy! Weasling out of things is important to learn. It's what separates us from the animals! Except the weasel." - Homer Simpson
Web - Blog - RSS - Math - LinkedIn - BM
|
|
|
|
|
People that handle economic issues is just too limited to imagine the possibilities. Just take the case of negative amounts. If you could issue a check with a negative amount, it would elliminate the need of invoices. Paying your rent would just be a matter of casching a negative check. 
---
It's amazing to see how much work some people will go through just to avoid a little bit of work.
|
|
|
|
|
Guffa wrote: Paying your rent would just be a matter of casching a negative check.
And how many people would cash it? 
"Marge, don't discourage the boy! Weasling out of things is important to learn. It's what separates us from the animals! Except the weasel." - Homer Simpson
Web - Blog - RSS - Math - LinkedIn - BM
|
|
|
|
|
It is not too small. The whole thing came up because apparently Verizon doesn't know the difference between cents and dollars; some guy was inquiring about data transfer rates while he was in Canada, and multiple times they quoted his rate as "0.002 cents/KB" when they meant "$0.002/KB", and consequently his bill was 100 times larger than he expected. He has chronicled the story on his blog: http://verizonmath.blogspot.com/[^].
--
Marcus Kwok
|
|
|
|
|
Can you pay a fraction of one cent ??
Luc Pattyn
|
|
|
|
|
I don't think so... as one of the Verizon reps said, "there is no .002 dollars"
--
Marcus Kwok
|
|
|
|
|
Verizon bad check fee: $40
Verizon late payment fee: $40
Bank bad check fee: $40
Messing with a minimum wage employee's mind: Priceless?
--
Rules of thumb should not be taken for the whole hand.
|
|
|
|
|
Classic!
But, IIRC, the Uniform Commercial Code (UCC) in the US spells out exactly how a financial must be written in order to be valid for a transaction, and this one fails the test. Not surprising, really, as 90% of my college math students had no idea how to correctly write a check in the legal format until we covered it in class. Given the right format, and the right information you can write a legally binding check on a bar napkin; without that, even a printed check does not have to be honored by the recipient if the format is wrong.
"...a photo album is like Life, but flat and stuck to pages." - Shog9
|
|
|
|
|
I seem to remember reading a story somewhere where a check was written on a piece of steel plating from a ships hull. The check weighed about 4 tons but was perfectly valid. The bank cashed it, then had a couple of security guards with Thompson submachine guns go out and cancel it!
Dave Kreskowiak
Microsoft MVP - Visual Basic
|
|
|
|
|
Dave Kreskowiak wrote: The bank cashed it, then had a couple of security guards with Thompson submachine guns go out and cancel it!
*cough* ricochets *cough*
Has to be an UL.
Besides, regardless of what the cult of 45 would like you to think about the rounds power, armor plate will deflect .50 machinegun rounds, never mind a handgun cartridge.
--
Rules of thumb should not be taken for the whole hand.
|
|
|
|
|
There was a picture of the check in the book with the two guys who canceled it. The bullets didn't have to go through the steel - just make dents in it. All it had to say was "canceled".
Prop the steel back far enough and the bullets go flying off into the distance (out into the harbor) instead of bouncing back at you.
Dave Kreskowiak
Microsoft MVP - Visual Basic
|
|
|
|
|
Hi Guys
I am relative new to Visual Studio... I'm about to do some calculations on my data and I was wondering if anybody can tell me the difference between choosing a Windows application or Console application when starting a project. Seems to me to be easier to implement my algorithms in a console, because it is possible to get the data output in the command-prompt (don't know how to do this in an application) and when doing the GUI I could change it over to an application, is this possible..?
Thanks in advance
AL
|
|
|
|
|
ComCoderCsharp wrote: Seems to me to be easier to implement my algorithms in a console...
Generally speaking, algorithms are not governed/affected by platforms. Perhaps you are referring to something completely different.
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
I think his point may be that in a console app you don't have to waste 80% of your time programming around the Windows overhead. For a straight "Run" type app, a console program is far more efficient.
"...a photo album is like Life, but flat and stuck to pages." - Shog9
|
|
|
|
|
Sounds like you want a console application.
|
|
|
|
|
I think you are trying to determine the diference between a Win32 application and a console application, right? There is a third option, which is an MFC application.
If you justo compute data then console is grat and MFC too. Simple Win32 applications start without any interface, so it will be dificult to interact with the users, even for a simple printf!
So, I would advise you to use console or MFC. Console is simpler and standard, MFC is easier if your input is composed of many parts with numbers, buttons, checkboxes, etc.
If you know nothing about MFC then your only real option is console.
I hope this helps,
Rilhas
|
|
|
|
|
Rilhas wrote: Simple Win32 applications start without any interface, so it will be dificult to interact with the users, even for a simple printf!
Same thing with MFC. 
Also, the project wizards for VS have long since generated skeleton apps for both Win32 and MFC. Don't get me wrong, I have nothing against MFC; I just don't want people to be steered wrong.
|
|
|
|
|
I'm sorry, but that is not true. An MFC application is much easier to startup that Win32.
An MFC application skeleton will typically create a window for you, which is the hardest step. Then you visually add a text box or whatever, and output to it using SetDlgItemText(). This is very simple. The corresponding simplest alternative in raw Win32 is the MessaBox (since we don't want to create a normal window) and this is not really equivalent because the program stops until the message box is dismissed.
The same applies to adding buttons and the like, which is done visually and a function is created for you. It is all automatic. I've been programming with MFC for years now, and I never learned how to do it... that goes to show how easy it is. My application work and allow data input and output, buttons, sliders, etc, without ever mastering MFC. With raw Win32 this would require much more work than I ever had with MFC.
So, I don't think I'm steering anyone the wrong way. On the contrary, I believe that anyone who needs a console application may do it with MFC. Interaction will surelly be easier, since making a bunch of text boxes and a start button is simpler and easier than a bunch of scanf's, and allows for an easier user interaction.
I can send you a simple hello world application based on a skeleton to which I add just 2 or 3 extra lines. With another 3 or 4 lines I can show the equivalent to scanf for inputing text. I bet you cannot do the same starting from a Win32 skeleton. At leaste not with lines as short as mine! In this sense MFC does rival to console applications (in the low number of lines required to startup a program).
Rogério Rilhas
PS: I assume the use of VC6 which has skeletons for both MFC and Win32, and what I say above applies to this scenario. VC7 or VC8 may have other skeletons (more ellaborate) for Win32, but I trust that even with these newer IDE's it will always be simpler to use MFC instead of Win32.
|
|
|
|
|
Rilhas wrote: I'm sorry, but that is not true. An MFC application is much easier to startup that Win32.
You're arguing apples to oranges. I never said MFC wasn't easier. You said, and I quote, "Simple Win32 applications start without any interface, so it will be dificult to interact with the users, even for a simple printf!" To that I said it's not true. I never said MFC wasn't easier to use.
Rilhas wrote: An MFC application skeleton will typically create a window for you, which is the hardest step. Then you visually add a text box or whatever, and output to it using SetDlgItemText(). This is very simple. The corresponding simplest alternative in raw Win32 is the MessaBox (since we don't want to create a normal window) and this is not really equivalent because the program stops until the message box is dismissed.
No offense, but you must be inexperienced. You may wish to try out that project wizard again for a Win32 app and notice it will create a window - which is what I said. Also, the dialog editor applies exactly the same way as it does for a MFC project.
What you're confusing is the amount of options the MFC wizard gives you compared to the Win32 one (ie, you can select a dialog-based app in the MFC wizard). Any dialog in Windows could make use of the editor no matter what framework. The Win32 wizard just gives you the option to create a normal window (think frame).
Rilhas wrote: I can send you a simple hello world application based on a skeleton to which I add just 2 or 3 extra lines. With another 3 or 4 lines I can show the equivalent to scanf for inputing text. I bet you cannot do the same starting from a Win32 skeleton. At leaste not with lines as short as mine! In this sense MFC does rival to console applications (in the low number of lines required to startup a program).
This only proves you have no clue what you're even arguing about.
|
|
|
|
|
You are missing the point. MFC is easier. MFC cannot be started without an interface. Win32 can. You can start Win32 with an interface, but it is much more hard to start a text interface. Of course this is the point, if comparing with console applications. So, don't forget, we are talking apples. Keep this in mind, and when you think I'm stearing anyone the wrong way then don't start talking oranges. Try to compare CON/MFC/WIN32 and you will, inevitably, conclude that the first 2 are much easier than the latter to setup (with skeletons) and use (in text).
So, you focused on the fact that it is possible to create a Win32 with a graphical interface, and lost focus that that is not the interface required for this comparison. You can then take the conversation through that lane, but you will be missing the point. I didn't mention that particular aspect because I thought is would be ovious (text interface, not graphical interface). And, again, don't forget the other benefits I mentioned like input text boxes and buttons.
I'm not inexperienced, so I take no offense. You just missed the point, and so you didn't understand what I meant. Maybe a problem in my English since it is not my native language. If you try to create a Win32 project with a window (in VC6) a graphical interface is created. You go to the dialog editor and draw a little button, just like with MFC. Then you try to create a callback function (you will need to add a class and some more steps) and then you find out it doesn't compile. Typically CDialog is undefined. Typically MFC does not present these problems. So if you think Win32 is an alternative to MFC in dialog (and button and textbox) creation then you are, of course, missing the point, and taking the discussion back to oranges.
No, I'm not condusing anything, I'm sure you are. But please: try to do an equivalent to printf and scanf in Win32 with VC6 with... say... 10 extra lines? 10 extra short lines? With a button, maybe? Or a checkbox? Please do, and then we will see which of us is confused.
I know what I'm talking about. You are the one singing off-key here. And you are the one misleading people.
|
|
|
|
|
Rilhas wrote: You are missing the point.
I'm not missing anything. What you said is incorrect primarily because you don't know what it is even that you're arguing, and you're arguing apples to oranges.
Rilhas wrote: MFC is easier.
Can you at least read my posts before you start arguing?
Rilhas wrote: MFC cannot be started without an interface.
More proof you don't know what you're talking about. At least get your terminology correct when you don't listen. You can create a MFC app without a GUI; however, the wizard doesn't give you that option.
Rilhas wrote: So, you focused on the fact that it is possible to create a Win32 with a graphical interface, and lost focus that that is not the interface required for this comparison.
You mean the comparison that you made that didn't even address my point? You were talking about wizards and so was I. I even quoted that. Then, your next statement was about how MFC is easier, blah blah blah.
Rilhas wrote: No, I'm not condusing anything, I'm sure you are. But please: try to do an equivalent to printf and scanf in Win32 with VC6 with... say... 10 extra lines? 10 extra short lines? With a button, maybe? Or a checkbox? Please do, and then we will see which of us is confused.
Ok, look I'll say this S-L-O-W-E-R! You're comparing apples to oranges just to argue a point I never made.
Rilhas wrote: I know what I'm talking about. You are the one singing off-key here. And you are the one misleading people.
Yeah, for a beginner you're gonna have a difficult time with an attitude like that. Good luck, you'll need it.
|
|
|
|
|
Yes, you missed the point. Proven again. What was the point? Remember? "When should I choose Windows application or Console application?". Remember why I brought up MFC? Just read back, don't make me re-type it.
MFC is easier (than Win32). This is the point. You missed it, argued wrong, and then didn't find a way to come back gracefully. Simple: just apologise. I read your posts. No apologies, they still say I was misleading. Well, it is easier, so where was I misleading? Oh, I know: you didn't understand the context of my sentence. Sorry, your bad.
The terminoloy is correct. I can even start and MFC application with hammer and nails. Yes. a Magnific Fine Chair. Oh, sorry, lost context. You mean MFC as in VC or MFC as in bricolage? Please: don't loose focus. Don't try to argue terminology, otherwise a can start arguing that MFC don't have graphical interfaces, just wood. You won't be able to contradict me, but we won't get anywhere.
OF COURSE MFC WITH A WIZARD!! At least MFC with a wizard is easier than Win32 in assembly. Do you agree or am I being misleading?
I'm not comparing apples to oranges. I was talking about apples. You started talking about oranges because you missed the context of my sentence (maybe just to say something). And you stated that I was misleading while talking of apples. And then you just keep on defending that it was a good idea to talk oranges. At the same time you say apples are good. I'm sorry, your comments are just pointless.
I'm not a beginner. Probably much more experienced than you and in many more areas. You just don't know, but you think you do.
|
|
|
|
|
Rilhas wrote: MFC is easier (than Win32). This is the point. You missed it, argued wrong, and then didn't find a way to come back gracefully.
You are one stubborn fool. What part of I never even bothered to address this point did you not get? And this time actually answer the question to prove you're even bothering to read my posts.
Rilhas wrote: MFC is easier (than Win32). This is the point. You missed it
That's nice. Enjoy your stay at the "I hate to listen" club.
Rilhas wrote: I'm not a beginner. Probably much more experienced than you and in many more areas. You just don't know, but you think you do.
If you're not a beginner then you're a slow learner. And after this thread, I can believe it.
|
|
|
|
|
Your correction to my post. This is the reason why. You missed the point and argued I was misleading. Is this enough for you to understand now?
I'm listening: what exactly have you said about this? Nothing. Still nothing. I sure would like to read you say that MFC is, in fact, almost as easy as CON, and Win32 is much harder (to use as CON). I'm still waiting. But you avoid a position on this. Of course, because if you said so then you would have to admit that your fisrt correction was out-of-place... and that it lost focus and missed the point. Maybe you could even say something like "What I wrote is true, but I now understand that it doesn't address your comments and that you were not being misleading... I just didn't understand what you meant right away". Should I wait sitting down? Enjoy your stay at the "I hate to speak" club.
I'm not a slow learner. But I'm a good learner. I typically don't throw myself inside large big holes on the ground like you did I try to crawl out still trying to look good.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
