8 Commits

Author	SHA1	Message	Date
mainzelm	8246b41681	Let UNCASE-CHAR-SET return a regular expression as promised in the manual.	2006-03-23 10:52:31 +00:00
mainzelm	c965536804	Cover 8 bits instead of 7 when converting from char-sets to regexps.	2006-03-23 07:59:14 +00:00
mainzelm	f4fbe4c986	(rx (| numeric alphabetic)) yields a char-set: but ... (rx (| ,(rx numeric) ,(rx alphabetic))) doesn't:, even though the "type-checking rules" for char-sets says that it should: > (rx (| numeric alphabetic)) '#{re-char-set} > (rx (| ,(rx numeric) ,(rx alphabetic))) '#{Re-choice} The following patch fixes this but I'm not sure if make-re-choice is the right place to tackle this problem: This fixes bug report #1063781	2005-10-18 14:01:50 +00:00
sperber	ce9da610e6	Handle the regexp matching the empty string specially, as POSIX ... requires it to be "()", not "()". This closes bug [ 1005026 ] sre: (** 0 0 "foo") raises error	2004-08-22 14:22:29 +00:00
mainzelm	da53963d82	Fixed a bug in the parser of "-" sre forms.	2004-01-09 22:51:07 +00:00
mainzelm	ed3cc365b0	Fix for ... > (regexp-search? (posix-string->regexp "$") "test") Error: exception wrong-type-argument (checked-record-ref '#{Unspecific} '#{Record-type 46 cre} 1) by Peter Wang	2003-10-23 15:58:08 +00:00
mainzelm	acb0c8265f	Fix for (rx (|)) by Peter Wang	2003-10-23 15:55:55 +00:00
mainzelm	3e397f65c5	GC_PROTECT some variables.	2003-05-01 10:21:33 +00:00