ordering FAQ

Are UNIX/Linux versions of your products available?

Contact sales@bytecraft.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).


Can my variables straddle resource boundaries?

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... 

Remember the compiler does not take any special precautions for variables whose address is specified using the @ operator.

The compiler can handle most of these situations transparently. To make absolutely sure:

  1. Program using proper C data types. In the situation above, use a union to overlay the variables.

  2. Avoid using the @ operator.

  3. Check the listing file: addresses for compiler-allocated variables appear at the left of the declaration.


Can the compiler generate an assembly source file?

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.


Is your compiler ANSI-compliant?

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.


What are the differences between the DOS and Windows versions of your products?

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.
  • The Windows compiler has a Windows-based development environment that provides quick and easy access to the compiler, the linker and to your other software tools. The DOS compiler has a much simpler shell which runs the compiler, editor and other tools. (You are not required to use either environment if you already have a preferred development environment.)

What are the restrictions on your demo software?

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.


What is your return policy?

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.


What support do you offer? What about upgrades?

For more information on this, see our order page.


Who distributes your products?

See Distributors for an updated list of distributors.