◄Up► ◄Contents► ◄Index► ◄Back► ─────Programmer's WorkBench───────────────────────────────────────────────── Defining a Build:message rule can be difficult. You have to work with the nesting of backslashes and the intricacies of regular expressions. See: ◄Tagged Expressions in Build:Message► Because backslashes have special meaning in both macro strings and regular expressions, it is easy to get the expression wrong. Predefined regular expressions can simplify your task. To match: Use the predefined expression: A filename \:p A line or column number \:z A token \:i See: ◄Predefined Regular Expression► When you define a new message rule, PWB adds it to the end of the list of message rules. You cannot delete any rules during the session. A mistaken rule can cause errors for the rest of the session, thus interfering with the iterative process of debugging a new rule. It is easier to debug the Build:message regular expression by defining a regular-expression find-and-replace macro and testing it with a file of sample messages. Once the regular expression is correct, you can define the actual rule. See: ◄Debugging a Build:message Rule► See ◄Tagged Expressions in Build:Message► -♦-