[mkgmap-dev] [PATCH v1] make DP filter avoid removingpointslocated at nodes
From Mark Burton markb at ordern.com on Mon Nov 23 14:10:09 GMT 2009
Hi Chris, > Interesting, I wonder when that changed? I'm fairly sure that never used > to be the case. I don't think it's something that you should rely on, especially > since the VM spec says the following: > > ... Here's something else I guess you shouldn't depend on: further experimentation shows that the order of the class member declarations doesn't make any difference to the object size. So you can intersperse the bools with the ints and the object size doesn't change. The Java compiler must order the fields to minimise the space required. That's fine because (not being C) you can't address the object's fields by pointer so the ordering is not visible to the programmer. Cheers, Mark
- Previous message: [mkgmap-dev] [PATCH v1] make DP filter avoid removingpointslocated at nodes
- Next message: [mkgmap-dev] [PATCH v1] make DP filter avoidremovingpointslocated at nodes
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list