2.3 Code editor

Code editor

The text editor included in CCE is a versatile tool and very effective for helping with the code editing task. The C/C++ perspective is shown in Figure 1 .

Cce workbench – c/c++ perspective.

The text editor has a set of features that allow speeding up the code editing process. An overview of the text editor is shown in Figure 2 .

Cce workbench – text editor window.

Code editing is greatly facilitated using features such as search and replace. To accomplish this task, the user must select Edit>Find/Replace . In addition to the normal features of search and replace, the option Search>File allows the use of more elaborate expressions. For example, it provides the global replacement in all files of a specific directory. The search and replace tasks previously performed can be found on the drop-list .

CCE can regularly save the opened files for editing in order to prevent losses caused by system crashes. To use this function, select Window>Preferences>General>Workspace and specify the time interval at which this task should be performed automatically. The project can also be saved whenever it goes through project build.

The content wizard is a very effective tool to support the writing of code. It is possible to automatically insert a code structure model, previously defined, as an alternative to writing it out completely (see an example in Figure 3 ). To insert a model of a structure, it is only necessary to write the first letters in the text editor and then press the Ctrl + Space keys in order to display a list of the corresponding models. The options in the list can be reduced by continuing writing the structure name. The Arrow Up and Arrow Down keys can be used to select the desired model and by pressing the Enter key to accept the selection. At any time the Esc key allows editing to continue without the use of the content wizard.

CCE workbench – Content wizard.

The behaviour of this feature can be configured in Window>Preferences . In Figure 4 shows the configuration page of the content wizard.

Cce workbench – preferences window.

The search range can be restricted to only the edited file and to the files included therein ( Search current file and included files ), or alternatively a search can be in the whole project ( Search current project ). Automatic model insertion is allowed, as long as it is the only one at the options list ( Insert single proposals automatically ). The user may also request that the suggestions list is presented in alphabetical order ( Present proposals in alphabetical order ). Another aspect that can be configured is related to the time (in milliseconds) that the content wizard delays to suggest a list ( delay ), or the duration of the validity of the suggestion ( Content Assist Parsing timeout ).

In addition to the sequence of Ctrl + Space keys, the content wizard can also be set automatically when the following characters are typed: " . ", " -> " or " :: ".

CCE is already provided with a set of models. However, it is possible to create new models by opening the models editor. Expand the C/C++ perspective in Window>Preferences , and select Editor>Templates . The option New must be selected to create a new model (see Figure 5 ).

Cce workbench – new template window.

A name must be given for the new model. The context in which the model is valid should be selected. In the Description field a brief description of the model can be added. The model itself is described in the Pattern field. To insert a variable, use the Insert Variable option.

One way to learn how to create models, or even how to customize existing models, can be achieved using the model editing feature (see Figure 6 ). To access this feature, the Editor>Templates option must be chosen, and is visible after expanding the C/C++ perspective in Window>Preferences .

Cce workbench – edit template window.

The procedures to check on this page are identical to those described earlier for building new models.

The CCE supports the following intrinsic functions for the MSP430 family devices:

- void __no_operation(void);

- void __enable_interrupt(void);

- void __disable_interrupt(void);

- unsigned short __get_interrupt_state(void);

- void __set_interrupt_state(void);

- void __op_code(unsigned short);

- unsigned short __swap_bytes(unsigned short);

- void __bic_SR_register(unsigned short);

- void __bis_SR_register(unsigned short);

- unsigned short __get_SR_register(void);

- void __bic_SR_register_on_exit(unsigned short);

- void __bis_SR_register_on_exit(unsigned short);

- unsigned short __get_SR_register_on_exit(void);

- void __set_SP_register(unsigned short);

- unsigned short __get_SP_register(void);

- unsigned short __bcd_add_short(unsigned short, unsigned short);

- unsigned long __bcd_add_long(unsigned long, unsigned long);

- void __data20_write_char(unsigned long, unsigned char);

- void __data20_write_short(unsigned long, unsigned short);

- void __data20_write_long(unsigned long, unsigned long);

- unsigned char __data20_read_char(unsigned long);

- unsigned short __data20_read_short(unsigned long);

- unsigned long __data20_read_long(unsigned long);

Request the MSP430 Teaching ROM Materials here (External Link)