|
-
Aug 16th, 2000, 02:34 PM
#1
Thread Starter
Lively Member
Do you have a rule over there that says "When in doubt throw in a 'u'"?
e.g.
color = colour
neighbor = neighbour
etc
Or is it that we (Americans) just remove 'u's whenever possible?
Probably the second one. I wonder what is the deal with our exclusion of the 'u'. Poor thing. I feel sorry for it.
-
Aug 16th, 2000, 02:38 PM
#2
Monday Morning Lunatic
It must be 2, because we had the language first . Although we do like to add a 'u' occasionally. Maybe in the days of telegrams, they shortened words, and dropped out non-essential letters.
I refuse to tie my hands behind my back and hear somebody say "Bend Over, Boy, Because You Have It Coming To You".
-- Linus Torvalds
-
Aug 16th, 2000, 03:51 PM
#3
Member
I'm fairly new to VB (using VB6), so when you say check to make sure they are the correct dll's how do I do that?
All I know is that I select the references from the list and then go about my business. I see it has the location of the reference at the bottom of the form but how do I know if it's the correct version?
Thanks.
-
Aug 16th, 2000, 04:00 PM
#4
transcendental analytic
You should have these checked in References,
Visual Basic For Applications
Visual Basic runtime objects and procedures
Visual Basic objects and procedures
OLE Automation
CHR$ function is in strings module in VBA library which is in this file:
VBA5.DLL ( I guess it's VBA6 for vb6)
you could need to register this one again
Use  
writing software in C++ is like driving rivets into steel beam with a toothpick.
writing haskell makes your life easier:
reverse (p (6*9)) where p x|x==0=""|True=chr (48+z): p y where (y,z)=divMod x 13
To throw away OOP for low level languages is myopia, to keep OOP is hyperopia. To throw away OOP for a high level language is insight.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|