flex/tests/posixlycorrect.rules
Eric S. Raymond a53aec8e86 Rulesets now carry their test loads with them.
Makes it easier to see what the tests are doing.
2020-10-31 18:19:29 -04:00

46 lines
1.5 KiB
Plaintext

/*
* This file is part of flex.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
*
* Neither the name of the University nor the names of its contributors
* may be used to endorse or promote products derived from this software
* without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
* IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
* WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
* PURPOSE.
*/
/*
* The goal of this test is to verify that we are getting the
* counter-intuitive POSIX behavior of the repeat operator `{}' when
* posix_compat is off but POSIXLY_CORRECT=1 is set in the
* environment. Note: This depends on the test framework to actually
* set that variable! When it does not, Flex will match abbb
*
* ab{3} - In traditional flex, this matches "abbb".
* In posix, this matches "ababab".
* The input file should contain just the second string.
*/
%option nounput nomain noyywrap noinput
%option warn
%%
ab{3} { }
\n { }
. {M4_TEST_FAILMESSAGE}
###
ababab