3/1/2024 0 Comments Php small caseDeclare Statements, Namespace, and Import Statements.Now I'm really done flogging this dead horse. This will/may be more an issue if/when scripting ever comes to Affinity applications. So when such a person is expecting Perl/Boost compliance comes to APub, threads such as this will be written wherein you (or others) can feel free to write the explanations of how to do it in APub. In the case of APub, there are X number of people coming from InDesign (and others) where such a flag (Match Case) isn't even present as the person doing/constructing the regex is expected to follow Perl/Boost regular expression syntax. It's not a big deal in the larger scheme of things-unless one is coming from other applications that interpret/implement the Boost library differently. We seem to simply disagree on how case classes are implemented and APub's requirement to also add the case flag sticky setting to do what a case class is intended to do without it. Now we could go on arguing what those statements mean and how they apply to APub.but that's mostly meaningless without one of the developers stepping into this discussion and explaining the rationale of their implementation of this/these features. The case sensitive flags are used for "literal strings" to allow, or disallow, case sensitivity. So I'll leave it at that.Īccording to the Boost documentation, ]/] are case classes that are "class names are always supported by Boost.Regex." ![]() So we differ on our opinion in this regard. You seem to shrug your shoulders over APub's inability to comply with the Boost library. I don't believe any other option-especially a half-hidden option that is sticky-should be needed in APub. My text editor also doesn't need the case sensitive flag when using an explicit case construction such as ] or ]. But it is unneeded (i.e., it doesn't need set to on) if I use a Perl case flag such as APub requires. Yes, my text editor also has a match case switch. Seems like we're going around in circles. I could probably test how Perl operates but I'm too lazy to do that right now, as I would have to relearn enough Perl to make that test. If you simply begin all regular expressions with either (?i) or (?-i) then you won't depend on the setting of the Match Case option in Publisher.Īs I mentioned, Boost seems to operate one way (as does Notepad++), Python another. So it's up to the user to be aware of the options he's chosen, or to specifically set them in the regex when it's important. ![]() And, apparently, when the "case insensitive" flag is turned on (or, Match Case is off in the Publisher Formatting options), ] will match upper- or lower-case characters, as will ]. (?-i) to do a case sensitive match (that is, the pattern "a" will not match "A").Īnd there isn't any flag necessary, but Publisher has one (as do other programs that support regex processing) and so you have to be aware of how it is set. This is the same as having Publisher's Match Case option off. (?i) to do a case insensitive match (that is, the pattern "a" will match either "a" or "A"). To avoid that possibility, you could start your regular expression with either: The only possible issue with a sticky option like that in Publisher, that I see, is that it's hidden and you might forget how you last left it set, unless you remember to look. There's no real choice for the programmer that option is either turned on explicitly, or turned off explicitly, or left to default to however the regular expression processor defaults it (either on or off). The program will invoke the regular expression processor with the "match case" flag either set on, or set off. Sticky settings, like this one, shouldn't be necessary.Įvery program that I've ever used that supports regex searching has a sticky setting like that, either explicitly or implicitly. ![]() However note that it is a setting that is sticky-i.e., persists until changed again.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |