Liren Large Software Subsidy 5

home *** CD-ROM | disk | FTP | other *** search

/ Liren Large Software Subsidy 5 / 05.iso / a / a034 / 2.ddi / ERRORMSG.TXT < prev next >

Wrap

Text File | 1994-02-02 | 18.4 KB | 697 lines

dBASE Compiler for DOS Error Messages ------------------------------------- This file lists the dBASE Compiler for DOS error messages in alphabetical order. If you get an error message that is not listed here, refer to Appendix G, "dBASE Error Messages," in the Language Reference. ')' missing in macro invocation MAKE error. Left and right parentheses are required to invoke a macro. For example: MACRO = DIR *.prg $(MACRO) #include: expecting a file name BDC error. Your program contains an #include preprocessor directive that doesn't have a file name specified. Argument mismatch BDC error. The arguments in a called macro do not match the macro's defined parameter list. For example: #define x(y) y ? x && missing parameter Bad filename format in include statement MAKE error. Include file names must be surrounded by quotes ("filename") or angle brackets (<filename>). The file name was missing the opening quote or angle bracket. If you used a macro, the resulting expansion text is incorrect, that is, it is not surrounded by quote marks. Bad macro output translator MAKE error. Invalid syntax for substitution within macros. For example: $(MODEL:=s) or $(MODEL:) or $(MODEL:s) Bad undef statement syntax MAKE error. An !undef statement must contain a single identifier (and nothing else) as the body of the directive. Can't create output file: <filename> BDC error. BDC could not create the preprocessed output (.dpp) file. You may have specified an invalid path with the -P or -p option, or your system may not have enough disk space. Can't find include file <filename> BDC error. Make sure you've used the correct include file name and/or path in your #include statement, or with the -I option. Can't open file: <filename> BDC error. You may have specified a file that doesn't exist. Cannot create <filename>! BDL, DSPLIT, or DJOIN error. BDL or DJOIN could not create the executable file, or DSPLIT could not create the file segments because: - You have specified an invalid path with the -E option (BDL) or -O option (DPSLIT or DJOIN) - There is an existing read-only file with the same name - Your system has run out of file handles. Cannot execute <filename>! Your executable file could not be executed. Your system may not have enough memory. Cannot have multiple paths for implicit rule MAKE error. You can only have a single path for each of the extensions in an implicit rule. Multiple path lists are only allowed for dependents in an explicit rule. For example: {path1;path2}.prg.dbo: #Invalid {path}.prg.dbo #Valid Cannot have path list for target MAKE error. You can only specify a path list for dependents of an explicit rule. For example: {path1;path2}prog.exe: prog.dbo #Invalid prog.exe: {path1;path2}prog.dbo #Valid Cannot open <filename>! BDL, DSPLIT, or DJOIN error. You may have specified a file that doesn't exist. Cannot split to more than 999 file segments! DSPLIT error. The file segment size that you specified with the -S option is too small. Enter a higher value so that DSPLIT creates fewer than 999 file segments. Cannot write to <filename>! BDL, DSPLIT, or DJOIN error. A write error occurred while BDL, DSPLIT, or DJOIN was writing to a file. If using BDL, this message is also displayed if you specified an invalid filename for the resulting executable file. For example, BDL @Allfiles -E Aux is invalid because "Aux" is a DOS device name. Circular dependency exists in makefile MAKE error. The makefile indicates that a file needs to be up-to-date before it can be built. Take, for example, the following explicit rules: file1: file2 file2: file3 file3: file1 This implies that file1 depends on file2, which depends on file3, and file3 depends on file1. This is illegal since a file cannot depend on itself, directly or indirectly. Colon expected MAKE error. You have forgotten to put the colon at the end of your implicit rule. .prg.dbo: #Correct .prg.dbo #Incorrect Command arguments too long MAKE error. The arguments to a command were more than the 128-character limit imposed by DOS. Command syntax error MAKE error. This message is displayed in the following cases: - The first rule line of the makefile contained any leading whitespace. - An implicit rule did not consist of .ext.ext:. - An explicit rule did not contain a name before the : character. - A command definition did not contain a name before the = character. Command too long MAKE error. The length of a command has exceeded 128 characters. You might want to use a response file. Corrupted <filename>! BDL error. DBASE.RTL is corrupted. Reinstall it from the product disk. Could not create temporary file <filename> MAKE error. MAKE was unable to open the necessary temporary file. The file may be read-only, or may be already open. Disk in drive <drive> is full! Please replace it with another disk! DSPLIT or DJOIN error. The target location you specified with the -O option does not have enough disk space for the file segment or reassembled file. Try a different disk. Disk is full! BDL, DSPLIT, or DJOIN error. The hard disk you are writing the file to does not have enough space. Disk is write-protected! BDL, DSPLIT, or DJOIN error. The disk you are writing the file to is write-protected. Division by zero MAKE error. A division or remainder operation in an !if statement has a zero divisor. Division by zero in #if BDC error. A division in an #if statement has a zero divisor. <filename> does not exist - don't know how to make it MAKE error. There is a nonexistant file name in the build sequence, and no rule exists that would allow the file name to be built. Drive is not ready! BDL, DSPLIT, or DJOIN error. Make sure you've inserted a floppy disk into the drive where you are writing the file to. Duplicate file <filename>! BDL error. You have specified an object file more than once. For example: BDL TEST TEST BDL TEST @FILELIST (and FILELIST contains TEST) Empty #if expression BDC error. You have used an #if directive without an expression. Expression parser: syntax error BDC error. BDC encountered an error while parsing an #if statement. For example: #if foobar() && foobar() is not defined Expression syntax error in !if statement MAKE error. The expression in an !if statement contains a mismatched parenthesis, an extra or missing operator, or a missing or extra constant. Extra chars ignored at end of line BDC warning. BDC ignored all characters after any conditional #if or #elif statements. File <filename> is already open BDC error. You are trying to compile a file that either "includes" itself or another file recursively, for example, TEST.PRG that contains #include "TEST.PRG". File not found: <filename> BDC error. BDC can't find <@filename>, the file that contains the list of files to compile. Filename too long MAKE error. The file name given in an #include directive was too long for the compiler too process. Path names in DOS must be no more than 79 characters long. If statement too long MAKE error. An if statement has exceeded 4,096 characters. Ifdef statement too long MAKE error. An ifdef statement has exceeded 4,096 characters. Ifndef statement too long MAKE error. An ifndef statement has exceeded 4,096 characters. Illegal character in constant expression <expression> MAKE error. MAKE encountered an invalid character in a constant expression. If the character is a letter, this probably indicates a misspelled identifier. Illegal octal digit MAKE error. An octal constant was found containing a digit of 8 or 9. Illegal parameter list in #define BDC error. The parameter list in a #define statement may be missing an ')' or you might have used a literal value in the parameter list. For example: #define VAR("x",y) DEF(v,w) && "x" is an invalid argument #define VAR(1) B(x) && 1 is an invalid argument Illegal usage of directives BDC error. You have used the directives incorrectly. For example: #define $ "hello" && Symbols such as "$" are invalid macro names #define #if if() && Cannot expand preprocessor directives Incorrect command line argument: <argument> MAKE error. You've used incorrect command-line arguments. Incorrect option specified.....<option>! BDL error. You have used a command line option that BDL doesn't recognize. Make sure you specify a valid option with the correct upper- or lowercase letter. Insufficient memory! BDC, BDL, DSPLIT, or DJOIN error. Your system doesn't have enough memory to run BDC, BDL, DSPLIT, or DJOIN. Int and string types compared MAKE error. You've tried to compare an integer operand with a string operand in an !if or !elif expression. Invalid file <filename>! BDL error. BDL links the following object files only: .DBO, .FMO, .FRO, .LBO, .QBO, .UPO, and .BIN. Filenames with other extensions are invalid. Invalid file name <filename>! BDL error. You have used an invalid character in your file list. For example: BDL TEST* The following are invalid characters: [, ], =, |, <, >, +, ;, *, ?, /, , Line too long BDC error. A command line in your program file exceeds 1023 characters. Macro expansion too long MAKE error. A macro cannot expand to more than 4,096 characters. This error often occurs if a macro recursively expands itself. A macro cannot legally expand to itself. Macro recursion BDC error. You are using a macro recursively. For example: #define ABC(x) ABC(x) ? ABC(2) Macro redefinition BDC warning. You have defined a macro more than once. For example: #define A "Hello" #define A "Bye" Macro replace text <string> is too long MAKE error. The macro replacement text <string> overflowed MAKE's internal buffer of 512 bytes. Macro substitute text <string> is too long MAKE error. The macro substitution text <string> overflowed MAKE's internal buffer of 512 bytes. Maximum number of nested compiler directives exceeded BDC error. You can have up to 64 nested levels. Misplaced elif statement MAKE error. An !elif directive is missing a matching !if directive. Misplaced else statement MAKE error. MAKE encountered an !else statement without a matching !if statement. An extra !else statement could cause this message, but it could also be caused by missing braces, or a syntax error in a previous !if statement. Misplaced endif statement MAKE error. An !endif directive is missing a matching !if directive. No closing quote MAKE error. There is no closing quote for a string expression in a !if or !elif expression. No filename ending MAKE error. The file name in an #include statement is missing the correct closing quote or angle bracket. No macro before = MAKE error. You must give a macro name before you can assign it a value. No match found for wildcard <expression> MAKE error. There are no files matching the wildcard <expression> for MAKE to expand. For example, if you write prog.exe: *.obj, MAKE displays this error message if there are no files with the .obj extension in the current directory. No matching #endif BDC error. Your program contains an #if, #ifdef, or #ifndef directive without a matching #endif directive. No matching #if BDC error. Your program contains an #endif directive without a matching #if directive. No terminator specified for in-line file operator MAKE error. The makefile contains either the && or << command-line operators to start an in-line file, but the file is not terminated. No valid dbo file specified! BDL error. You have not specified any .DBO files for BDL to link. Not enough memory MAKE error. Your system doesn't have enough memory to execute MAKE. Only <<KEEP or <<NOKEEP MAKE error. You have specified something besides KEEP or NOKEEP when closing a temporary inline file. Option <option> not valid with <option> BDC error. You have specified conflicting options. For example, you may have used the -c option (compile only) and specified linker options, or the -P option which tells BDC to write preprocessed output, but not to compile. You may also have used the -L (create standalone executable) and the -S (create compact executable) options. Premature EOF BDC error. BDC expected more lines of code to follow a command line that ended with a semicolon (;). Redefinition of target <filename> MAKE error. The named file occurs on the left side of more than one explicit rule. Rule line too long MAKE error. An implicit or explicit rule was longer than 4,096 characters. Specified split size is invalid! DSPLIT error. You must enter an integer value for the -S<segment size> option. The following, for example, are invalid values: x, 1.44, 0.5. Specified split size is too large! (max 2GB) DSPLIT error. The value you enter for the -S<segment size> option cannot exceed 2GB. Specified split size is too small! (min 1KB) DSPLIT error. The value you enter for the -S<segment size> option must be equal to or greater than 1. Split size is larger than <filename> itself! DSPLIT error. The value you entered for the -S<segment size> option is larger than the file you are trying to split. String type not allowed with this operand MAKE error. You have tried to use an operand which is invalid for comparing string types. Valid operands are ==, !=, <, >, <=, and >=. Too many <option> options BDC error. You have specified more than 256 -D (define) statements in your configuration file. Too many files to process BDC error. BDC can compile up to 2500 files. Too many suffixes in .SUFFIXES list MAKE error. You have exceeded the 255 allowable suffixes in the suffixes list. Unable to execute command: <command> MAKE error. A command failed to execute; this may be because the command file could not be found, it was misspelled, there was no disk space left in the specified swap directory, the swap directory does not exist, or (less likely) because the command has been corrupted. Unable to open file <filename> MAKE error. You may have specified a source file that doesn't exist or is in use. Unable to open include file <filename> MAKE error. The compiler could not find the named file. This could be caused if an !include file included itself, or if you do not have FILES set in CONFIG.SYS on your root directory. Check if the named file exists. Unable to open makefile MAKE error. The current directory does not contain a file named MAKEFILE, MAKEFILE.MAK, or does not contain the file you specified with -f. Unable to redirect input or output MAKE error. MAKE was unable to open the temporary files necessary to redirect input or output. If you are on a network, make sure you have rights to the current directory. Unexpected end of file MAKE error. The end of the makefile was reached without a temporary inline file having been closed. Unexpected end of file in conditional started at line <line number> MAKE error. The source file ended in the middle of a comment. This is normally caused by a missing close of comment (*/). Unknown directive BDC error. You have used a directive that the preprocessor doesn't recognize. Check your program file for mistyped directives. Unknown option: <option> BDC error. You have used a command line option that BDC doesn't recognize. Make sure you specify the option with the correct upper- or lowercase letter. Unknown preprocessor statement MAKE error. A ! character was encountered at the beginning of a line, and the statement name following was not error, undef, if, elif, include, else, or endif. Unterminated macro call BDC error. Your program contains a macro call that is missing the closing parenthesis. For example: #define x() y ? x( Unterminated parameter list BDC error. A macro call requiring a parameter list is not terminated properly; a closing parenthesis may be missing. For example: #define ABC(x) DEF(x) ? ABC(2 Unterminated parameter list in #define BDC error. A macro definition with a parameter list is not terminated properly; a closing parenthesis may be missing. For example: #define A(x, B(x) Unterminated string BDC error. A preprocessor statement is missing the closing quote ("). For example: #include "filename Use of : and :: dependents for target <target> MAKE error. You have tried to use the target in both single and multiple description blocks (using both the : and :: operators). Examples: filea: fileb filea:: filec Write error on file <filename> MAKE error. Your hard disk may contain bad sectors.