On Sun, Oct 01, 2000 at 02:30:39PM -0600, Nathan Torkington wrote: > Nathan Wiger writes: > > > True, C<> and E<> are pretty warty, but they clearly identify > > > something more presentational in nature. > > > > Yes, this is true. I think it's pretty apparent that the <> syntax is > > broken - there's too much stuff (like -> and <>) that uses duplicate > > characters. This could be solved if escapes worked: > > > > C<foo-\>bar> > > This is solved in 5.6 and later's POD: > > C<< foo->bar >> > > If you squint, you can see those French chevrons poking out. No-one ever did suggest adding « and » to the list of matched delimiters that q() etc support, did they? :-) Does Unicode define bracket pairings for character sets? <ducks> Nicholas Clark
- RFC 357 (v1) Perl should use XML for documentation ins... Perl6 RFC Librarian
- Re: RFC 357 (v1) Perl should use XML for document... Adam Turoff
- Re: RFC 357 (v1) Perl should use XML for docu... Frank Tobin
- Re: RFC 357 (v1) Perl should use XML for ... John Porter
- Re: RFC 357 (v1) Perl should use XML for ... Adam Turoff
- Re: RFC 357 (v1) Perl should use XML ... Nathan Wiger
- Re: RFC 357 (v1) Perl should use... Nathan Torkington
- Re: RFC 357 (v1) Perl should... Nicholas Clark
- Re: RFC 357 (v1) Perl sh... John Porter
- Re: RFC 357 (v1) Perl sh... Tom Christiansen
- Re: RFC 357 (v1) Perl should use XML ... Damien Neil
- Re: RFC 357 (v1) Perl should use... Glenn Linderman
- Re: RFC 357 (v1) Perl should... Damien Neil
- Re: RFC 357 (v1) Perl sh... Bart Lateur
- Re: RFC 357 (v1) Perl sh... John Siracusa
- Re: RFC 357 (v1) Perl sh... Tad McClellan
- Re: RFC 357 (v1) Perl sh... Bart Lateur
- Re: RFC 357 (v1) Perl sh... Tad McClellan