Betascript Publishing CRiSP File Editor 6 Manual de usuario Pagina 15
- Pagina / 92
- Tabla de contenidos
- MARCADORES
Valorado. / 5. Basado en revisión del cliente
Page 15
ready for loading into CRiSP. The crunch program uses its own internal preprocessor which is very ANSI-C
like. By doing this gives the user more portability of macros and avoids common differences between
standard preprocessors.
Next the intermediate file is converted directly to the binary output file. Crunch has a number of switches:
-c Compiles the source file to a .m file. This is useful for understanding the translation process
or to check for bugs in the compiler. If you have any problems understanding what crunch is
doing, then use this switch.
-Dvar Used to #define constants before preprocessing. This switch is passed directly to the
preprocessor.
-f Used to flush output during debugging. Causes the output to be written to the terminal. This
is useful if crunch core-dumps and you want to try and ascertain at what point during code
generation the problem is occurring.
-Ipath Add a path to search for include files. This switch is passed directly to the preprocessor.
-g Used to insert debugging information into the compiled code. This includes line number
information, so that when a macro error occurs, CRiSP can report the line in error.
-m This is the make flag. Tests the modification time of the output file versus the source file and
only recompiles if it is necessary. This allows trivial makefiles to be built rather than having to
face the bugs in standard make. (See the distribution makefile how to use this).
For example, you can say:
crunch -m -o /macrodir *.cr
and only the out of date macro files will be recompiled. (No account is made of dependencies
on include files).
-n Print out the names of files which would be compiled, but don't compile them. This flag is
useful with the '-m' (make) flag to verify what files will be recompiled.
-o file Specifies the name of the output file to create. The file parameter can be the name of a
directory in which case the output file is put into the specified directory.
-p cpp Used to specify the path of the C preprocessor to execute if the one on your system does not
conform to the standard used by the current Unix versions, e.g. if you are using Turbo C, or
you have a POSIX compliant C compiler.
-q If more than one source file is specified on the command line, crunch normally prints the
name of each file as it is being compiled. This switch can be used to turn off this feature.
-S Special non supported feature. Used to dump a symbol table.
-Uvar Make the named variable undefined. Passed directly to the C pre-processor.
-V Prints version number of compiler.
-# Prints each pass of the compilation process as it proceeds.
The crunch compiler more or less understands the full ANSI C syntax, including structure definitions, bit
fields and typedefs. However, crunch is really only designed to accept macros which can be used by CRiSP.
At present CRiSP cannot handle structure and typedef definitions and so it is best to avoid these.
The crunch compiler normally creates a temporary intermediate file between the pre-processing stage and
the compilation phase. Normally this file is created in /tmp. You can override this by specifying the name of a
directory in either the CRTMP or TMP environment variable. (CRTMP will take precedence if both are
specified).
{button See Also, ALink(crunch,,,)}
Data types
CRiSP supports a range of primitive data types and complex objects. The following is a summary of the
basic data types:
Type Description
- CRiSP File Editor 1
- Programmers Guide 1
- Introduction 7
- Disclaimer 7
- Writing your own macros 9
- Tools Overview 10
- <Alt-F10> 10
- File formats 11
- Specifying Directories 11
- Language Mapping switches 11
- General switches 11
- Output file format 12
- Filename filtering 12
- Language specifications" 13
- Languages 13
- The CRUNCH Language 14
- The crunch compiler 14
- Data types 15
- Scoping 17
- Argument Passing 18
- Variable argument lists 20
- The int data type 21
- The float/double data type 21
- The string datatype 21
- The list (array) datatype 22
- List assignment 23
- Making Lists 23
- Manipulating List Items 24
- Sorting Lists 24
- Searching Lists 24
- Informational Lists 24
- The declare datatype 25
- Structures 25
- Language Grammar 25
- Declarations 26
- Function definitions 27
- Expressions 27
- Testing expressions: if 29
- Selection: switch 29
- Debugging macros 30
- Macro tracing 31
- Debug applied to a function 32
- Debug on startup 32
- Debug buffering 33
- The vars() macro 33
- Buffers, Files and Windows 33
- Buffer Attributes 34
- Ansi Mode buffer attribute 34
- The Backup Flag 34
- The Binary Flag 34
- Character Maps 37
- Objects supported by CRiSP 38
- Backing up Files 39
- Autosaving 39
- Core dumping 40
- Regions and markers 40
- Global and Static macros 41
- Registered Macros 42
- Timer functions 45
- Color Support 46
- Character Escaping 48
- Character Class: [..] and 49
- Matching Line boundaries 49
- Repetition: @ and + 49
- Minimal and Maximal Matching 50
- Matching Direction 51
- GUI Based Objects 51
- Terminology 52
- Overview of an Object 54
- Creating a Dialog Box 55
- Object Types 56
- Geometry Layout 59
- Sub-groups 64
- Properties (private symbols) 65
- Dialog boxes and Callbacks 66
- Platform Specific Issues 67
- Keyword Builder 68
- Character classes 69
- Global attributes 69
- Keywords 69
- Creating a new colorizer 69
- Dialog box buttons 69
- .KWD Keyword File Format 70
- The flags= Directive 71
- Character Class Directives 72
- Keyword Directives 74
- Keyword Flags 75
- Keyword Regular Expressions 76
- Limitations of Colorization 76
- Colorization:limitations 76
- Case study #1: C colorizer 77
- IPC Mechanisms 79
- IPC Primitives 80
- IPC Callbacks 80
- IPC_TRIGGER_WRITE 82
- Pipe Communications 84
- PTY Communications 84
- PTYPseudo 84
- Server:DDE 85
- DDE Communications 85
- DDEProgram Manager 85
- Excel:invoking CRiSP 86
- Signals Communications 86
- Signal based communication 87
- Keyboard objects 87
- Keys and Keystrokes 88
- Character based terminals 88
- Scan Codes 89
- The cm compiler 90
Comentarios a estos manuales