The very existence of flamethrowers proves that at some time, some where, some place, someone once said to themselves "I'd really like to set those people on fire over there, but I just can't get close enough".
There are only two hard things in computer science: cache invalidation, naming things, and off-by-one errors
SCJP 1.4 - SCJP 6 - SCWCD 5 - OCEEJBD 6 - OCEJPAD 6
How To Ask Questions How To Answer Questions
There are only two hard things in computer science: cache invalidation, naming things, and off-by-one errors
Originally posted by fred rosenberger:
you could always pretend like java started with 1... as long as you declare your arrays bigger than you really need them.
[OCP 21 book] | [OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Originally posted by Pat Farrell:
Why did C do it? Because C is just PDP-11 assembly language with some minor syntactic sugar. Assembly languages always use zero based.
Originally posted by Guido Sautter:
Hi Fred,
what do you mean "we're cursed with int, float, etc."?
There are only two hard things in computer science: cache invalidation, naming things, and off-by-one errors
Originally posted by Jeanne Boyarsky:
Of course, this isn't such a good idea when you work on a team since your teammates will be using the standard convention of starting with zero.
There are only two hard things in computer science: cache invalidation, naming things, and off-by-one errors
Some problems are so complex that you have to be highly intelligent and well informed just to be undecided about them. - Laurence J. Peter
Some problems are so complex that you have to be highly intelligent and well informed just to be undecided about them. - Laurence J. Peter
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |