At 06:52 -0700 6/11/09, Jonathan Pool wrote: >> We've found that hiring someone who's willing to study the ins >> and outs of the language in question and implement an expert >> solution has worked very well > >Except when it hasn't. BBEdit mistreats Perl regular expressions.
I'm stuck on OS 10.3.9 for hardware reasons so I can't contribute much but. . . Someone might like to check for syntax coloring, in perl, of the << operator meaning a binary shift left. There is confusion in another editor (OK, it's gedit) with the perl usage of the same symbol pair for introducing a perl-style HERE document. Figuring a workaround is painful because one really has to look ahead for the ending string that terminates the HERE string after a few line ends. There is a convention in gtksourceview that syntax coloring is defined in an XML file named perl.lang and similarly for other languages. The format is a fairly nasty list of regular expressions with defined variables that are handled by the display code. I was able to muck with perl.lang and repair the display for my own purposes but the result isn't perfect because it places restrictions on just what can be in a HERE document. Well: they're deprecated in the Camel book. Someone has said "only perl can compile perl." I agree. -- Applescript syntax is like English spelling: Roughly, though not thoroughly, thought through. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BBEdit Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/bbedit?hl=en If you have a specific feature request or would like to report a suspected (or confirmed) problem with the software, please email to "[email protected]" rather than posting to the group. -~----------~----~----~----~------~----~------~--~---
