No. The compiler does not generate an intermediate assembly source file. The compiler and linker have built-in macro assembly functionality, so a separate assembly source file is not necessary. The assembly found in the listing file is actually a disassembly of the generated opcodes.
In general, no. Boundaries created by the hardware or instruction set restrict how the compiler can allocate variables.
Wherever an architecture uses pages or other interrupted address spaces, there is the potential that a variable will straddle such a boundary. The risk is greatest when you specify the address of a variable in terms of another:
int one; //in one area int two; //in another area long three @ one; //oh oh...
Byte Craft Limited compilers have not been certified as ANSI-compliant, and we do not advertise compliance. However, we have used the ANSI C specification in developing our C compilers since the draft standard was first made available, and we continue to participate in software standards discussions via the Standards Council of Canada. Most ANSI C conforming programs can be compiled by our compilers.
For more information on this, see this page.
Demonstration versions of the software are restricted to generating up to 2K words of object code, and will not generate an executable. The BClink linker is not included.
For more information about the restrictions, see the
readme.txt file that appears in the installation directory.
For more information on this, see our order page.
Our products come with a 30-day money-back guarantee. Contact us in writing (by email or fax) with your reason for the return, within 30 days of purchase, and we will forward instructions for returning the product and obtaining a refund.
Contact email@example.com for information on UNIX versions.
Remember that Windows emulators/environments such as WINE are available. We have run our products under WINE with some success (and some odd quirks).
The DOS and Windows versions of our compilers have the same set of supported features (source code compiled with one will be identical to source code compiled with the other), but differ in the following ways:
- The Windows compiler supports Windows long file names; the DOS compiler does not.
See Distributors for an updated list of distributors.