The SilverC Compiler

The first version of the SilverC compiler, a K&R version, was written in 1987. The first program was an Othello game program.  This program survives today both as a SilverC and as a SilverSharp demo program. In 1994, the compiler was updated to near ANSI compliance under the DOS version of the SilverScreen Solid Modeler. In 1995, with the advent of Windows 95, the compiler was upgraded to run under Windows.

The compiler produces a byte code execution file, similar to Java.  At execution time, the file is interpreted by a software interpreter. This means that SilverC programs will execute more slowly than native C/C++. However, in most programs, the execution of ss_command statements is the dominant factor in determining execution speed. In these programs, there is little perceptible difference between SilverC and native C/C++.

SilverC provides an add-in facility within the SilverScreen interactive environment. SilverC programs are executed from SilverScreen and, at completion, return to SilverScreen.

SilverC: Advantages

SilverC is very efficient development environment with quick compiling, testing and code revision. It is an ideal tool for small to medium sized projects. Windows-style user interfaces may be assembled easily and quickly using the SilverC library. This may be done with no understanding of Windows programming and C++.

Since SilverC code can be easily ported to SilverPlus and SilverEngine, developers often use SilverC as a tool for quick prototyping. In the early stages of development a simple user experience is sufficient for the purpose of a feasibility study or communicating ideas with non-technical, but interested parties.

SilverC: Disadvantages

Here are the three areas where SilverC is somewhat weak:
 

SilverC: Overall

Developers give high ratings to SilverC. They particularly appreciate the speed of development. They also appreciate being able to  accomplish a great deal without getting entangled in the complexities of Windows programming.