Skip to content

Commit b78d4ed

Browse files
committed
Increase max identifier length from 64 to 128
To allow compiling updated winapi headers which contain at least one identifier with 68 chars: GUID_PROCESSOR_CORE_PARKING_OVER_UTILIZATION_HISTORY_DECREASE_FACTOR It shouldn't cause any problems to increase this limit besides a tiny increase in the compiler's total memory usage, since it's only used with static strings or the symb.namepool which, however, assigns ids into multiple "length categories" and allocates the best fit, as opposed to allocating the maxlen everytime.
1 parent f91f496 commit b78d4ed

File tree

2 files changed

+2
-1
lines changed

2 files changed

+2
-1
lines changed

changelog.txt

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ Version 1.01.0
33
[changed]
44
- On Linux/*BSD, the FB runtime will now delay using VT100 terminal escape sequences to query terminal window size and cursor position until the first use of a console I/O command (previously it was immediately done at startup, always, even if the FB program didn't use any of FB's console I/O commands)
55
- WITH ... END WITH blocks now have an implicit scope, like SELECT, DO ... LOOP, etc. Variables declared inside will no longer be visible outside.
6+
- Identifier length limit increased from 64 to 128 (due to Windows API headers which contain at least one identifier with 68 chars)
67

78
[added]
89
- On Linux/*BSD, the FB runtime will now respect the __fb_enable_vt100_escapes global variable (also see examples/console/disable-vt100-escapes.bas). FB programs can set it to 0 (FALSE) in order to manually disable the use of hard-coded VT100-specific escape sequences by FB's console I/O commands. This can help getting FB programs to run on older terminals which don't accept these escape sequences. However, it may also cause FB's console I/O commands and functions to behave differently. For example, if the use of the escape sequence for querying cursor position is disabled, then the FB runtime will assume that the cursor starts out at position 1,1 even if that is not actually true.

src/compiler/fb.bi

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ const FB_MAXNAMESPCRECLEVEL = 64
3333
const FB_MAXARRAYDIMS = 8
3434
const FB_MAXDEFINEARGS = 32
3535

36-
const FB_MAXNAMELEN = 64
36+
const FB_MAXNAMELEN = 128
3737
const FB_MAXLITLEN = 1024 '' literal strings max length
3838
const FB_MAXNUMLEN = 64
3939
const FB_MAXOPERANDLEN = FB_MAXNAMELEN + 2 + 16 + 2 + 1

0 commit comments

Comments
 (0)