Printable View
I thought it was English, but after looking it up the translation appears to be pineapple, not grapefruit. It's only the English who seem to want to do it different from the rest of Europe (as usual : they drive on the other side of the road and the metric system is new to them). It is called ananas or very similar in Danish, Dutch, Estonian, Finnish, French, German, Italian, Polish, Portuguese, Spanish, Swedish, Turkish and even in Arabic, Hindi, and Urdu.
In Africa pineapple is called nanas. I am sure it came from ananas. Strange, the name is almost global :eek:
In Spanish is ananás, but... it is most known like piña :)
From Simon:
I know about the story of Joan of Arc, kid! I read it up once, kid!Quote:
You don't know much about European history, don't you? Why didn't you just call it St. Joan of Arc's barbecue if you want to be very sadistic?
I dunno the full exact happenings, but I know she's a brave warrior who fought for the French army(against the British, I think) and got termed as a witch in the end and got burned at the stake alive. Hmmm...kinda sad......it depends on how you think it, kid!
If you wanna see things from a total pervert's viewpoint, no one can stop you, right? If you're thinking dirty all the time, again, no one can control your thinking. If you see a black-color coated computer and you think of it as Satan, who can stop you? :roll eyes:
No.....not really........ananas doesn't remind me of female bodyparts. It reminds me of male bodyp.......u get the idea.Quote:
An ananas is a piece of fruit. Have you really never heard of it? It is typical of you though to think of female bodyparts again.
Cos' logically, ananas is related to banana, and as u know, banana.........ummm.........u get the whole idea. :D:D:)
Then it is not smart - if not intended - or else sadistic - if intended - of you to mention her in a context of frying, which she did herself.Quote:
Originally posted by Xeon
I know about the story of Joan of Arc, kid! I read it up once, kid!
Because banana = b + ananas - s does not mean that two words are logically or elseway related in English.Quote:
Originally posted by Xeon
Cos' logically, ananas is related to banana, and as u know, banana.........ummm.........u get the whole idea. :D:D:)
I think Simon has been vindicated :oQuote:
Xeon says No.....not really........ananas doesn't remind me of female bodyparts. It reminds me of male bodyp
Aye Simon! :p:p
Anyway, Platinum pal......."vindicated"??!!
Whoa! U really gotta send me 10 plates of chicken chop every 5 days! Why? Cos' your English level has improved dramatically since you met me! Cool! :)
Huh, yes you are right, it's pineapple, not grapefruit. I guess grapefruit came to my mind since I absolutely hate it :pQuote:
Originally posted by Simon666
I thought it was English, but after looking it up the translation appears to be pineapple, not grapefruit. It's only the English who seem to want to do it different from the rest of Europe (as usual : they drive on the other side of the road and the metric system is new to them). It is called ananas or very similar in Danish, Dutch, Estonian, Finnish, French, German, Italian, Polish, Portuguese, Spanish, Swedish, Turkish and even in Arabic, Hindi, and Urdu.
And for that matter, we call it ananas in Luxembourg too :p
I just wonder to what extend VB and VC/C++ is used and how they overlap.
May I ask how you voted and what type of programs are you making?
As for me, I voted "VB Only". I'm into Marketing Information systems such as Market Planning, Market Research, Sales/Promotions tracking - pharmaceutical based. These are primarily database programs.
Additionally, I programmed mainly in Excel-VBA (seldom in full packaged VB) because my products are used primarily in the field by salesmen, auditors and researchers.
What about you please?
Ok guys, its not easy for me to write a friendly letter down here, but all i want to say is...
...I love to be a part of this forum cause actually has very serious members with a lot of experience and mature thinking first of all.
In DOS' days all my friends saying to me to learn something more than GWBasic, QBasic, even Turbo Pascal. But in this modern time we live its easy for everyone to see that the final common costumer wants something beautifull in his/her screen, animated puppets and 500 progress bars running simultaneously and showing some action (no care for fanatic speed, unless you are targetting polyethnic companies).
Visual C/C++ are tough languages... The only thing that could make me to look there is the compiler's speed. BUT, thanks to INTEL we have today extremely fast CPUs, GPUs and other smart boards, and all this together "encrypts" in some way the most important "bad" thing of Visual Basic, the execution speed of the compiled programs. Run a visual C++ program on a Pentium II machine, and a VB program on a Pentium 4 system. Which is the faster? :-p
I love so much VB, even my nephew can understand a visual basic program by seeing it in the IDE! Also thanks to the ACTIVEX technology there is no way turning my eye somewhere else: Just find the right OCX (if you cant do it by APIcalls or your own) and do what you want.
I cant forget my enthousiasm when i saw in VB5 the ability of writing a keyword and immediately the environment to showing me the right list of parameters, other options etc.
In college time I used to program in Assembly, even using DEBUG.COM, just by reading a Peter Norton's book. It was fun, to talk to the CPU and registers so straight.
But we are living in Microsoft days guys, the old DOS days with just a floppy aboard on the system are gone forever. Now all we have to do is to press the right buttons and run the right wizards.
DOS programs written for example in Turbo Pascal are CPU-dependent -only-. Now in windows our programs written through this modern IDEs the actuall thing they are doing is to manage ready-made windows function calls. Try to replace "kernel32.dll" with one you made (when in DOS clear mode). Of course consider first of putting in the new kernel the same functions and parameters, but having different results. And after that run Adobe Photoshop... Its possible for then to have a game-pacman on the screen instead of a picture processor.
Can i throw away my tears now? :)
Its good to have you all!!!
~poof~
From Danish TV:
How sweet, cute and sentimental! I......u......u-u-u.....make me cry! Argh booo hoo hoo! :(:(:(Quote:
Can i throw away my tears now?
Its good to have you all!!!
Are you a cute li'l girl, or a hot hot lady?! :eek::eek:
The compiler speed is irrelevant. I think you mean the speed of the compiled code, don't you? ;)Quote:
Originally posted by dtv
But in this modern time we live its easy for everyone to see that the final common costumer wants something beautifull in his/her screen, animated puppets and 500 progress bars running simultaneously and showing some action (no care for fanatic speed, unless you are targetting polyethnic companies).
Visual C/C++ are tough languages... The only thing that could make me to look there is the compiler's speed.
It is true that Intel has a couple of GPUs, but these are far from being the best around (e.g. see nVidia)Quote:
BUT, thanks to INTEL we have today extremely fast CPUs, GPUs and other smart boards,
Not exacltly a fair comparison. It's like with the hare and the turtle, except that the turtle rides an express train :)Quote:
and all this together "encrypts" in some way the most important "bad" thing of Visual Basic, the execution speed of the compiled programs. Run a visual C++ program on a Pentium II machine, and a VB program on a Pentium 4 system. Which is the faster? :-p
You know, many ActiveX controls are written in C++ ;)Quote:
I love so much VB, even my nephew can understand a visual basic program by seeing it in the IDE! Also thanks to the ACTIVEX technology there is no way turning my eye somewhere else: Just find the right OCX (if you cant do it by APIcalls or your own) and do what you want.
The VC IDE does that too.Quote:
I cant forget my enthousiasm when i saw in VB5 the ability of writing a keyword and immediately the environment to showing me the right list of parameters, other options etc.
We both know that it is not true what you are saying.Quote:
In college time I used to program in Assembly, even using DEBUG.COM, just by reading a Peter Norton's book. It was fun, to talk to the CPU and registers so straight.
But we are living in Microsoft days guys, the old DOS days with just a floppy aboard on the system are gone forever. Now all we have to do is to press the right buttons and run the right wizards.
DOS programs written for example in Turbo Pascal are CPU-dependent -only-. Now in windows our programs written through this modern IDEs the actuall thing they are doing is to manage ready-made windows function calls.
Replacing kernel32.dll is only possible if you write the new one in C ore C++. And it will probably get you a system crash instead of Pacman. :DQuote:
Try to replace "kernel32.dll" with one you made (when in DOS clear mode). Of course consider first of putting in the new kernel the same functions and parameters, but having different results. And after that run Adobe Photoshop... Its possible for then to have a game-pacman on the screen instead of a picture processor.
Don't take my post too seriously -- I'm just playing the devils advocate.
On a more serious note: VB has some major advantages (production speed, ease of learming it) but it doesn't render C/C++ useless. I can easily name things that can be done with C/C++ but are impossible in VB.
Cheers
This is my first time to post in this thread so give way to a kid:D..
My favorite language is C/C++ but there's something I couldn't resist in vb - The drugs called RAD!!!:D:D
From Thread1:
I really love humble guys like you, Thread! :):)Quote:
This is my first time to post in this thread so give way to a kid..
You see, not everyone knows how to respect the big boys.
Dunno who the big boys are? They're XeOn, Gabriel and Brad.
The others....they're just boys and men. :cool::cool:
Oh yes.....but they have the girls too, so everyone is happy and everyone wins. :D:D:)
Generally, VB is much easier and faster to make programs. But if you know a lot of C++, especially MFC, you can make programs in C++ as almost as fast as VB. They only have small time difference.Quote:
Originally posted by Thread1
My favorite language is C/C++ but there's something I couldn't resist in vb - The drugs called RAD!!!
Yes, I agree with you that you can not beat VB in terms of production speed. That's true because you use that bunch of OCXs/DLLs and make your program dependent to each and everyone this programs that if only one of these is misssing, then you cannot run your program anymore. But if you decided to use API calls instead of OCXs/DLLs or if your program can only be done in API calls, then C++ will beat you.
When I started as a programmer using VB language, I said this language is very great. I programmed many apps in using this language. But, the time I learned C++, I found those many bugs and limitations in VB. You cannot do those system level things in your VB code. You cannot make drivers!!!!. You are fast in VB but you dont have the power!!!
Have you not heard of win32 Assembly???? Don't say that you erased all your knowledge you acquired in your college days.Quote:
Originally posted by dtv
In college time I used to program in Assembly, even using DEBUG.COM, just by reading a Peter Norton's book. It was fun, to talk to the CPU and registers so straight.
But we are living in Microsoft days guys, the old DOS days with just a floppy aboard on the system are gone forever. Now all we have to do is to press the right buttons and run the right wizards