Overview

SourceBoost IDE (Integrated Development Environment) is a low cost development environment for Microchip Inc. PIC and Ubicom Inc. SX processors. SourceBoost IDE includes a modern editor, project manager, C, C++ and Pascal cross-compilers, Project wizard, assembler level debugger, clock accurate simulator and a number of virtual devices.

Index

Getting Started

SourceBoost IDE was designed to be easy to work with. It usually takes only a few minutes from SourceBoost IDE installation to the point when a compiled code runs on a target. Just remember that SourceBoost IDE works with projects only and even if you need to build one file you first have to create a project that will contain this file. Fortunately SourceBoost IDE supports multiple easy and fast ways to create new projects. 

Follow these steps to set up a new project:

• Open one of the sample projects that were installed with the SourceBoost IDE. For these sample projects look into the Samples sub-directory in the directory where you installed SourceBoost IDE.

• After the installation the BoostC toolsuite will be selected. If you want to use another toolsuite select one from the Active Toolsuite Selection dialog accessible from the Settings Toolsuite... menu:
  

• By default SourceBoost IDE uses the BoostC compiler toolsuite. This new generation C compiler generates all output files and doesn't need any third-party applications except programmer. However if you use the previous generation compilers like C2C-plus, C2C++ or P2C-plus you will need an external assembler as these compilers generate assembly files that need further assembling using third-party tools. All access to third-party tools is done from SourceBoost IDE Options dialog. To set up a command line for a third-party tool use the menu Settings Options...

  

  that will open the Options dialog, than go to the Tools page and verify that the paths and command line options to the external tools are correct (See also Building a Project - Assemble):
  

• Verify that the target processor is set correctly. The current target is displayed in the SourceBoost IDE Status bar. If necessary change the current target in the Target dialog that can be opened from the Settings Target... menu:
  

• Verify that the Build command starts compiler and linker in the Build Options dialog that can be opened from the Settings Build menu:
  

• Click the Build button on the SourceBoost IDE Tool bar. This will compile and assemble the current project and invoke the programmer for the target.

  At this point the current project should have been built and the target processor programmed. Its now ready to test!

SourceBoost Architecture

Supported Toolsuites

User Interface

SourceBoost IDE has a number of different windows dedicated to perform some specific functions. All of these windows may be docked inside the main SourceBoost IDE window or freely float at any part of the screen. 

The SourceBoost IDE may work in two modes:

• Edit mode when the project gets edited. 
• Debug mode that starts when a debug session is started. 

The windows that can be displayed and the layout of the windows is different for these modes. For example the Register, Stack windows are not displayable hidden in Edit mode, but can be displayed  in Debug mode.

In many windows right-click menues can be used. Remember, right-click menues are your friends. Often they offer features not available from main menu.

Tool Bar

	Create a new document file. The created file will have no syntax coloring utill it's been saved.
	Open an existing document file.
	Save the active document file.
	Save all modified document files.
	Cut selection.
	Copy selection.
	Paste content of the clipboard.
	Print the active document.
	Show/hide the Workspace window.
	Show/hide the Output window.
	Build the current project. This command starts the actions defined in the Build dialog.
	Compile the current project.
	Assemble the current project using external assembler. If the external assembler is not specified this button is grayed out.
	Start an external programmer. If the external programmer is not specified this button is grayed out.
	Start an external simulator. If the external simulator is not specified this button is grayed out.
	Display SourceBoost IDE About dialog.
	Start built-in debugger. SourceBoost IDE enters the Debug mode.
	Toggle a breakpoint on the line under cursor. Breakpoints can be set only in assembly files.

By default the tool bar is docked on the top part of the main window. However it may be docked on the bottom, left and right part or float outside of the main window.

Project Workspace Window

The IDE has a workspace window that can display either the Project files (that is the files a project  is composed of),. or a browser showing the various symbols used inside the Project files .

Switch between the file view or the browser view by using the tabs at the bottom of  the window.

Use right click menu to open, delete or add new files to a project.

Project Output Files

Files inside the Output folder are the output files generated during compilation or assembly.  By default these are the files in the project directory that have the same name as the project,  but with file extensions .asm, .lst and .hex.  To change what files are displayed in the Output folder list,  right click on any point inside the Workspace window and select the Customize Workspace... menu. This will display the Customize Workspace dialog with a list of files separated by commas to show inside the Output folder. The file names can contain paths that can be absolute or relative to the project directory.

It's a good idea to use symbolic names. The symbolic names will be substituted with real values that depend on project settings: %name% project name (i.e. my_long_project_name) %shortname% short project name (i.e. my_lon~1) %target% target name (i.e. PIC16F84) %shorttarget%   short target name (i.e. 16F84) %appdir%   SourceBoost installation directory (i.e. C:\Program Files\SourceBoost) When used to specify an application it's a good idea to enclose the whole path into double quotes (i.e. "%appdir%\ezdownloader.exe").

Browse Data

SourceBoost IDE has a built-in browser that automatically builds a database of symbols used in the current project.  This data base gets updated every time a project is loaded or a file inside the project is changed.

Double click on any symbol inside the browse window to open or activate a file where this symbol is defined.

Output Window

The Output window contains three pages. The Build page is used to display various messages produced by SourceBoost IDE, the Find page displays the results of the Find In Files command and the Terminal page allows to exchange data with a serial port.

Build Page

This page displays compilation and assembly output, error and warning messages and other information that may be interested to the user.

Double click on a compile error or warning to open or activate the relevant location in a source file.

Use F4 to navigate between error and warning messages.

Find Page

This page lists all files that are the result of the Find In Files command.

Double click on an item in this list to open or activate the relevant file.

Terminal Page

This is a serial port terminal. This page displays data received from a serial port and allows to send data to a serial port.

The Terminal page can be used to communicate with a bootloader.

If you use debug print in your target code it's convenient to use the Terminal page to display these debug strings.

Register Window

The register window shows registers for the current target. Based on their functionality, the registers are partitioned into groups.  This window functions only in debug mode and shows values of the target registers.  The format of each value may me changed using the right click menu. By default a register value is displayed in black but if it has changed since the last stop the value becomes blue.  To change the value click on it, enter a new one and press Enter or click anywhere.  To set a watchpoint on a register use the right click menu. A set watchpoint is indicated by a small red dot in the left top corner of a register name.

To change format of all registers keep the Ctrl key presses when selecting the format from the right click menu.

To change how the registers are partitioned edit relevant .TDF file that is inside the config sub-directory in the directory where SourceBoost IDE is installed.

Watch Window

The watch window functions only in debug mode and is used to display values of various symbols from the debugged code.  To add a new watch use the right click menu and select the Add... item. This will open the Quick Watch dialog where a new symbol to watch is specified. Similarly an already existing watch can be edited by selecting the Edit... item from the right click menu. A watch inside this dialog can be either entered or be chosen from the drop down list.

To change format of all watches keep the Ctrl key presses when selecting the format from the right click menu.

To add a register watch use a dollar sign in front of register name. To add a watch on a register number use a dollar sing in front of the decimal register address.

Stack Window

The stack window functions only in Debug mode and displays the content of the target hardware stack.

Double click on an item in the list to open or or activate the relevant location in a source file.

Memory Window

The memory window functions only in debug mode and displays the register map of the current target.  By default register values are displayed in black but if some have changed since the last stop their background becomes cyan. If a value was changed by user its background becomes green.  To edit the value of a register click on it, enter a new value and press Enter or click anywhere. To add a watch to a register use the right click menu.  A set watchpoint is indicated by a small red dot in the left top corner of a register value. Registers unimplemented for the current target have gray background.

Eeprom Window

The eeprom window functions only in debug mode and displays the eeprom map of the current target.  By default eeprom values are displayed in black but if some have changed since the last stop their background becomes cyan. If a value was changed by user its background becomes green.  To edit eeprom value click on it, enter a new value and press Enter or click anywhere.

Code Window

The code window displays the project listing file (if it exists). In debug mode execution line is displayed in this window as well as in a relevant source window. In debug mode when the code window is active all step commands are done on assembly level.

For toolsuites that generate call tree and code/memory usage data the code window will add tabs to display this information:

	Assembly mixed with sources.
	Program call tree.
	Code and memory usage by functions.

Profile Window

The profile window functions only in debug mode and displays in graphical and numerical forms the number of times every assembler label was hit during execution.

Double click on an item in the list to open or or activate the relevant location in a source file.

Window Positioning Tips

Hold down the Ctrl key while dragging a window to prevent it from docking. Try it!

Status Bar

Status Bar displays various IDE status information as current line and column, typing mode (insert or overwrite), number of clock cycles passed since the last reset etc.

Edit Mode

Edit mode is the default state of the SourceBoost IDE. When SourceBoost IDE starts it starts in the Edit mode. In this mode you can create or open projects, edit and compile code, start external tools etc.

Managing Projects

SourceBoost IDE works with projects. A project is a collection of source files, rules how these files should be compiled and some other information. A project has to be created even if the project only contains one source file. SourceBoost IDE allows multiple ways to create new projects. 

Quick Project

The Quick project creation is used when a project contains only one source file. In this mode just a source file gets selected and the project that has the same name as this source file gets created and opened inside SourceBoost IDE. Such project gets created for the last selected target.

New Project

This is a conventional way to create a new project. After selecting of the directory where the new project should be created and the project name an empty project gets created. 
To add files into this project use the Add file(s)... menu item in the Project menu or the right click menu of the Workspace window.

Project Wizard

In this mode a new project gets created from a template selected in the Project Wizard. The created project is ready to be compiled and run on a target:

Existing Project

An existing project can be edited by adding or removing files from it.

Not only .C, .CPP or .H files may be added to a project. It can be any file type i.e. readme.txt

Editing Code

The editor has been designed to make code editing as easy as possible. It features customized coloring schemes, indentation lines, hot keys, drag and drop, virtually unlimited undo/redo, autocomplete, function prototype call tips etc.

Syntax Coloring

An open document file is colored based on its extension. Files with .C, .CPP and .H extensions are colored by the SourceBoost IDE as C files. Files with .ASM, .S and .LST extensions are colored as assembly files. All other files are not colored. The current syntax coloring scheme, font, and some other editor parameters can be changed from the Editor settings dialog ( locate under main menu Setting Editor...).

Hot Keys

Code editing becomes much more productive when using editor hot keys (combination of keys that initiate various editor commands). SourceBoost IDE supports most of the standard as well as some unique editor hot keys. Some of them are listed below:

Autocompletion

Autocompletion is an editor ability to display a list of possible symbols for a partially typed symbol. 
To activate the autocompletion press Ctrl+Space, SourceBoost IDE than scans its symbol browse database and displays a list of symbols that match a partially typed symbol.

Function Prototype Hits

If a function with an existing prototype in a header file is being edited a tooltip will show this function prototype with the highlighted current parameter:

Make sure that header files are added to the project.

File Under Cursor

If there is a file name under the cursor, the right click menu will show an item to open this file in editor.

This may be handy when opening a file from an #include directive.

Matching Brace

When caret is positioned right before a brace this brace pair gets highlited. Pressing Ctrl+] moves the caret to the matching brace.

Source/Header Switch

If one of the source/header file pair is edited the right click menu will show the item Swap source/header to open this file pair.

Bookmarks

To quickly navigate between different parts of a big file bookmarks can be used. Press Ctrl+F2 to set a bookmark on the current line. To jump to the next bookmark press F2 and to jump to the previous bookmark press Shift+F2.

Folding

Folding allows to collaps portions of code to improve overall code readability. The pictire shows the rc232.c sample code with all functions except printf collapsed. Folding can be enabled or disabled in the Editor Settings dialog.

Clicking on the folding margin with Ctrl and Shift keys pressed expands or collapses all folding points.

Folding works only in the high level language sources like C, C++ or Pascal. It will not work in assembler or text files.

Right Click Menu Goodies

The right click menu of the source window contains many useful items that make your life easier:

Beside the standard operations like Copy and Paste this menu allows:

• access the Find and Replace dialogs;
• jump to the definition of a word under cursor even if this definition is in another file;
• jump to a label or symbol in the current file;
• in debug mode add the word under cursor to the Watch window. (When selecting this menu item press Ctrl to display the Quick Watch dialog);
• access list of functions (for C or C++ file) and labels (for ASM file).

If right click menu is called when the Ctrl button is pressed the menu will contain of functions (for C or C++ file) and labels (for ASM file).

Building a Project

SourceBoost IDE can work with different toolchains. the BoostC C compiler compiles C code directly into .HEX file and doesn't need any external tools. C2C-plus or C2C++ compilers compile C or C++ code into assembly language and P2C-plus compiler compiles Pascal code into assembly language. Then this assembly language file needs to be assembled into data (usually this is a .HEX file) that can be programmed into a target. Because SourceBoost IDE doesn't include assembler an external has to be used. Starting from version 5.3 SourceBoost IDE also supports PICC Lite compiler from HI-TECH Software. 
For the PIC target recommended assemblers are MPASM that is a part of MPLAB from Microchip and GPASM that is a part of GPUTILS. 
SourceBoost IDE  also does not include programming application. There is no recommended programmer software since almost all available on the market can be used. The only requirement of the external programming application is its ability to open an input file passes as one of its command line parameters. Similar requirement exists for an external simulator.

Don't confuse external simulator with SourceBoost IDE built-in debugger and simulator.

Build

Build performs multiple operations from one action. This allows the compile, assemble, program and simulate commands to be executed sequentially from one click of the build button. Only the operations checked in the Build dialog will be performed.

Staring from the version 5.2.2 SourceBoost IDE uses make to build a project. When user issues a build command SourceBoost IDE creates a makefile that contains rules enabled in the Build dialog and than calls make. Make than compares the time stamp of the input and output files for each rule and calls an action associated with a rule only if input files are newer than output files. Thus if a project was already compiled and it's sources weren't changed the build command will not compile it again.

Sometimes it's useful to rebuild the whole project even if some project files don't need to be processed. To force full project build use the hot keys Ctrl+F7 or Ctrl+build command.

The Simulate option here will invoke an external simulator, not the SourceBoost IDE debugger and simulator.  The SourceBoost IDE debugger and simulator are invoke by pressing the debug button on the tool bar.

Compile

Compilation converts C or C++ code into an assembly file. The structure of the generated assembly code depends on the compile and optimization options. 
The default options will work for virtually any project but sometimes it may be useful to change the settings based on the project needs:

Assemble

This command starts an external assembler using a command line specified in the Options dialog.

The C2C-plus, C2C++ and P2C-plus language toolsuites need an external assembler to convert the assembly file that these compilers generate into a hex file suitable to uploat into a target. The most commonly used external Assembler is MPLABs MPASM. Assuming it is installed in the default location, the command line options required for that assembler is:  C:\PROGRA~1\MPLAB\MPASMWIN.EXE /aINHX8M /p%target% /rHEX /w2 /q

Don't forget to add double quotes around the assembler executable if path to this executable contains spaces. For example: "C:\Program Files\MPLAB.6.30\MCHIP_Tools\MPASMwin.EXE" /aINHX8M /p%target% /rHEX /w2 /q

Program

This command invokes an external programmer application using a command line specified in the Options dialog.

The exact programmer command line depends on the programmer software you use. Here are some sample command lines: JDM programmer: C:\DOCUME~1\Yod\Desktop\winpic\WinPic.exe /p / device=%target% /q pp06 programmer: ppwin -! -hw 6 -lax IC-Prog programmer: C:\Pic\PROGRA~1\icprog.exe -l%name%.hex -f3F32 -p -q -i -v sxtips or sxdev programmer: "C:\Program Files\SourceBoost\SXTIPS\SX_TIPS.EXE" 2 P.EXE or sx_tips.exe \2\p PBrenner 3.2u programmer: "c:\programme\pbrenner\PBrenner32u.exe" /P%shorttarget% /F%name%.hex /A Quasar Electronics All Flash USB programmer: Micropro.exe %name% %target% /f /Q Picall programmer: C:\PICALL\PICALLW.EXE %name%.hex -e -p -v -x -d%target% You may need to change the path to programmer software and don't forget to add double quotes around the programmer executable if its name or path to this executable contains spaces!

Simulate

This command starts an external simulator application using a command line specified in the Options dialog.

Printing and Print Preview

SourceBoost IDE features document printing accessible from the File menu:

A printed document can have user defined header and footer and fully customizable margins:

Debug Mode

SourceBoost IDE has a built-in source and assembler level debugger and clock accurate simulator. Stepping depends on the active toolsuite. BoostC toolsuite supports source level debugging. PICC Lite toolsuite also supports source level stepping. The C2C-plus, C2C++ and P2C-plus toolsuites support assembly level stepping only.

A debug session is started by pressing the Debug button - See Tool Bar. This command starts the built-in debugger and simulator, loads the project .HEX file, resets the target and loads the Debug mode window layout.

Debug session can also be started and stopped using hot keys:

Debug session can be started only if the current project has been compiled and assembled.

Execution line

The execution line shows the position in sources and code windows that correspond to the current PC (program counter) and is highlighted with green color:

Debug Bar

The Debug bar is shown when SourceBoost IDE is in Debug mode. The buttons on the Debug bar Are mapped to various debug commands:

	Step Over	The Step Over commands executes the current instruction. If the current instruction is a call instruction the debugger doesn't step into this call but waits till the execution returns from this call.
	Step Into	The Step Into commands executes the current instruction.
	Step Out	The Step Out command executes instructions till a return from a call instruction gets executed.
	Step Back	The Step Back command returns the target to the state when it was stopped previous time. This command is unique to SourceBoost IDE, most other debuggers don't have it.
	Run	The Run command continues execution.
	Stop	The Stop command stops execution. This command is active only when target is running.
	Reset	The Reset command resets the target.
	Profile	The Profile command activates target profiling. Make sure that the Profile window is open.
	Snapshot	The Snapshot command activates updates of the Register, Memory, Stack and Watch windows. This command is active only in debug mode.

Debug Hot Keys

Debug hot keys make debugging more efficient. Some of these hot keys duplicate the functionality of the buttons on the Debug Bar and some are unique:

Breakpoints

Breakpoints can be added to at any line of a .asm file that contains an assembly language instruction.
Move the cursor to the line where a breakpoint is required and press the breakpoint button on the tool bar or press the F9 key.

Use the View menu or press Ctrl+B to open the Breakpoints dialog to see a list of the breakpoints that exist:

Double click on a breakpoint in the breakpoint list to position on the line in the source file where this breakpoint is set.

Watchpoints

A watchpoint allows the execution of the program to be halted when a register changes in value. Set watchpoints for registers can be set through either the Register window or the Memory window.

Symbol Value Hover

To quickly check the value of a symbol hold the mouse pointer over this symbol for more than 1.5 seconds. The symbol value will be shown in a tooltip near this symbol:

Plugin System

SourceBoost IDE features an extendable plugin system where each plugin emulates a physical device connected to the target. The standard SourceBoost IDE installation includes the following plugins:

	Single LED
	Block of 8 LEDs
	Single button
	Block of 8 buttons
	7 segment and 12 segment Display with decoding
	Speed Tester plugin to measure code execution speed
Digital Volt Meter Signal generator Logic Analyzer I2C EEprom Stop Watch LCD Display Analogue Voltage Source	Part of SourceBoost IDE Extra plugins package (http://www.picant.com/c2c/download.html)

Every plugin is connected to a target port and when the target is running each plugin changes its state based on the changes of the port it is connected to. The port value can also be changed by a plugin (for example the button plugin changes the value of the pin it is connected to).

To change the port a plugin is connected to or plugin settings (i.e. colours) use plugin right click menu that will display a plugin Configuration dialog:

Some plugins depend on the simulation clock rate that can be changed in the Clock Rate dialog accessible from the Settings Clock Rate... menu:

For more information and additional plugins description look into the Plugin System help file.

Appendix A: SourceBoost IDE Simulator features

The latest SourceBoost IDE Pic simulator now supports simulation of the following hardware devices that reside inside PIC micro-controllers:

Instruction Core - Including:

• ALU
• W register
• STATUS register
• Program counter
• FSR register
• RAM File Registers
• Stack

Interrupt Control - Including:

• Multiple sources of interrupt
• Accurate interrupt latency

EEPROM - Full implementation, includes:

• Write failure when correct programming sequence not followed

A/D convertor - only PIC16F877A and compatible types, includes:

• Choice of analog sources
• Selectable voltage references

Timer1 - 16 bit timer/counter, includes:

• Internal clock source
• External clock source
• Interaction with CCP1 and CCP2

Timer2 - 8 bit timer/counter, includes:

• Internal clock source
• Interaction with CCP1 and CCP2

CCP1 and CCP2 - Capture and Compare 1 and 2, includes:

• Capture Mode
• Compare Mode
• PWM mode

PortA - General purpose I/O port. Full I/O port implementation including:

• RA4 current sinking only
• Analog input capability (for devices with supported A/D convertors)

PortB - General purpose I/O port. Full I/O port implementation including:

• Interrupt RB0
• Change of state interrupt
• Weak pull-ups

PortC - General purpose I/O port. Full I/O port implementation including:

• Peripheral input/out features

PortD - General purpose I/O port. Full I/O port implementation

PortE - General purpose I/O port. Full I/O port implementation

PortF - General purpose I/O port. Full I/O port implementation

PortG - General purpose I/O port. Full I/O port implementation

Simulator Limitations

• EEPROM - write times may not be accurate.
• Timer 1 - External oscillator not support. There is currently no way to connected the required components. External Clock mode IS supported.
• PortF - Electrical interface currently modelled as PortC (not as actual device)
• PortG - Electrical interface currently modelled as PortC (not as actual device)
• Simulation of In Circuit Programming ports not supported.
• A/D convertor - Only 16F877A and compatible devices supported.
• Convertion times may not be accurate. Premature reading of A/D conversion value registers does not give same results as the actual device.

Appendix B: Toolsuite API

SourceBoost IDE was designed to be independant from toolsuites it uses as much as possible. Each such toolsuite consists of a DLL with well defined API. Though this API is not publicly available we are open for cooperation should you decide to integrate your toolsuite into SourceBoost IDE.

Appendix C: Debugger and Simulator API

In the SourceBoost IDE package the ide, debugger and simulator are logically and physically separated and communicate with each other trough well defined API. Such separation makes the whole system extremly flexible for future extensions. For example adding ICD support to SourceBoost IDE will require replacing of the simulator DLL with another DLL that implements simulator API from one side and talks to ICD hardware from another while neither ide nor debugger need any changes. Another example may be integration of gnu toolchain (gcc, gdb etc.) into SourceBoost IDE. This will require replacing the debugger DLL with a DLL that talks to gdb and writing a toolsuite DLL that will manage gcc compiler. Though these APIs are not publicly available we are open for cooperation should you decide to integrate your tools into SourceBoost IDE.

Appendix D: SourceBoost IDE setup for PICC Lite compiler

SourceBoost IDE installation includes a sample project for PICC Lite compiler. The project is located in the Samples\Picc.Lite sub-directory in the directory where SourceBoost IDE is installed (the default SourceBoost IDE installation directory is C:\Program Files\Picant). Go to the ProjectOpen... menu:

and navigate to the directory where SourceBoost IDE is installed and than to its Samples\Picc.Lite sub-directory:

. When project is open verify that the PICC Lite toolsuite is selected. Go to the SettingsToolsuite... menu:

and select the Picc Lite Toolsuite:

Than make sure that IDE knows where to look for the PICC Lite compiler. Go to SettingsOptions... menu:

select the Tools page in the Picc Lite compiler options dialog and enter the full path to the PICC Lite compiler in the Compiler field:

That's it. Now you are ready to edit, build and debug your project.

Appendix E: Older SourceBoost IDE releases

Appendix F: SourceBoost IDE and other compilers and tools

Purchase Information

SourceBoost IDE, C2C-plus, C2C++ and P2C-plus compilers are distributed as shareware products with a trial period (usually 15 days) to try these applications. After the trial period expires only PIC16F84 target remains supported. To unlock other targets SourceBoost IDE and at least one compiler must be registered. To register visit http://www.picant.com/c2c/register.html or send an e-mail to support@sourceboost.com. After registration an e-mail will be sent to you with a key used to unlock the product.

Beta release of BoostC C compiler is distributed free for both commercial and non commercial use. It will remain free till the first commercial release of BoostC is available. Once the commercial release of BoostC gets released you must stop using all previous releases of BoostC and remove them from your computer.

Legal Information

  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

  THE AUTHOR RESERVES THE RIGHT TO REJECT ANY LICENSE (REGISTRATION) REQUEST WITHOUT EXPLAINING THE REASONS WHY SUCH REQUEST HAS BEEN REJECTED. IN CASE YOUR LICENSE (REGISTRATION) REQUEST GETS REJECTED YOU MUST STOP USING THE SourceBoost IDE, BoostC, C2C-plus, C2C++ and P2C-plus COMPILERS AND REMOVE THE WHOLE SourceBoost IDE INSTALLATION FROM YOUR COMPUTER.