Hi
I would like to see the ability to have the compiler expand string
constants as follows in the next version:
Note that this is not only useful for includes (I know I could
use relative paths as offset from the WINAPI includes directory
but it's a pain to have to type in the same things all the time.
This gets especially painful with regular expression constants.
The ability to define constants as follows would be very helpful:
$WHITE_SPACE = "[\t\r\n]"
$OPTIONAL_WHITE_SPACE = $WHITE_SPACE + "*"
$TAG_FIND = "[a-zA-Z][-.a-zA-Z0-9]*"
$ATTRIBUTE_FIND = $OPTIONAL_WHITE_SPACE + $TAG_FIND + $OPTIONAL_WHITE_SPACE _
+ "=" + $OPTIONAL_WHITE_SPACE + "(\q.*>|[-a-zA-Z0-9./:+*%?!()_#=~]*))>"
Cheers
Florent
------------------
I would like to see the ability to have the compiler expand string
constants as follows in the next version:
Code:
$USER_INCLUDES = "c:\develop" $INCLUDE_MEM = $USER_INCLUDES + "\mem.inc" #INCLUDE $INCLUDE_MEM
use relative paths as offset from the WINAPI includes directory
but it's a pain to have to type in the same things all the time.
This gets especially painful with regular expression constants.
The ability to define constants as follows would be very helpful:
$WHITE_SPACE = "[\t\r\n]"
$OPTIONAL_WHITE_SPACE = $WHITE_SPACE + "*"
$TAG_FIND = "[a-zA-Z][-.a-zA-Z0-9]*"
$ATTRIBUTE_FIND = $OPTIONAL_WHITE_SPACE + $TAG_FIND + $OPTIONAL_WHITE_SPACE _
+ "=" + $OPTIONAL_WHITE_SPACE + "(\q.*>|[-a-zA-Z0-9./:+*%?!()_#=~]*))>"
Cheers
Florent
------------------