Own IWBasic 2.x ? -----> Get your free upgrade to 3.x now.........
Started by AdrianFox, February 19, 2009, 01:33:49 AM
0 Members and 1 Guest are viewing this topic.
Quote from: AdrianFox on February 23, 2009, 01:28:29 AMDon,As Paul has said above, the pdf file is located in the EBDev/help folder. I just printed out the relevant sections from the Ebasic Users Guide in the program.
Quote from: Paul Turley on February 23, 2009, 09:34:54 PM? I think you are a little confused on how an executable is made, and what determines it's final size. Nasm is just the assembler and it has little to do with the final size of an executable. An assembler takes mnemonic assembly code and translates it into machine code, in the form of a binary object file. The mnemonic code is produced by the Emergence BASIC lexer/parser, which we traditionally call the "compiler". Although it is common for the term "compiler" to refer to all of the tools needed to take a high level source code, such as BASIC or C, and produce an executable for it.
QuoteThe operand size of any particular mnemonic is constant, as specified for Intel processors. What that means is it doesn't matter what assembler you use, the size of the executable is determined by the number and size of each instruction plus the size of any linker included references plus the size of initialized data. Uninitialized data doesn't take up any space in the executable. In other words:string astring %b="hello"The first variable is just marked as "needing" 255 bytes when the executable is loaded by Windows. The second is initialized data, which takes up 255 bytes in the executable.