On Nov 4, 2007 11:57 PM, Bert Freudenberg <<a href="mailto:bert@freudenbergs.de">bert@freudenbergs.de</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>One thing that is odd not about the FAQ but about our beloved VMMaker<br>tool is that the "64-bit VM?" check box in VMMaker actually governs<br>building support for a 64-bit image, to use the FAQ's terms:
<br><br>"What is a 64-bit image? A 64-bit image is an image in which the<br>object memory uses a 64-bit word size for object pointers"<br><br>"What is a 64-bit VM? A 64-bit VM is one which is compiled with the
<br>LP64 or ILP64 data model"<br><br>So IMHO we should change that check box label to something indicating<br>"64-bit image support" to reduce a major confusion point. Putting a<br>link to the FAQ (or even a copy of the FAQ) into the tool itself
<br>might be an extra bonus.<font color="#888888"></font></blockquote><div><br>I agree. I found the name of this checkbox confused me no end.<br>It's what forced me to write the FAQ! Please let's give it a better name.
<br><br>While still on the topic of 64 bits, ...<br><br>- Is there a list of which plugins still need to be fixed to work in a<br>64-bit VM?<br><br>- Is there a (programmatic) way to find out if a given plugin will work<br>
in a 64-bit VM? (e.g. compile-time errors, or the absence of them?)<br><br>- Is there a set of guidelines on what to fix when porting a plugin?<br><br>(I guess this stuff should also go in to the FAQ...)<br><br>Andrew<br>
</div></div>