Different programs for composing, analyzing, and testing regexes support different dialects. RegexBuddy supports most dialects but there are other programs, free both as in freedom and as in price (or at least one of the two, sometimes) that support fewer but may do what you need.
But your regular expressions are in PHP code, right? Or am I missing something? Are they given as input to something implemented in PHP, rather than being as part of its implementation?
If you have the code that they are being used in, you can check what regex dialect is being used.
That's enough to know the dialect. One of the paragraph on that page says:
> The oldest set of regex functions are those that start with ereg...
(and describes it)
Let's see...
So I don't actually know php at all btw. Is any part of that string quoting? Or is everything that appears between the opening and closing double quote marks the regular expression?
Btw, meta question, and you don't have to answer it now: if I move this conversation to another room later, normally I'd move it to the Island, but would you prefer it go to the general room because you'd discussed this regex there previously? If you have zero preference either way I'd move it to the Island (when I move it) but I'm totally willing to move it to AUGR if you prefer.
and hes using some kind of editor who alows him to put text on top and regex on the bottom, i have to try the regex examples from this book still with the atom-plugin
Do you need to actually access the text captured by () groups, or are the parentheses just for grouping and not capturing? Like, are you just validating strings, or are you extracting things from them?
The actual full official syntax for email addresses is quite complicated, and even allows for quoting portions of the address. Is there a subset of permitted email addresses that you wish to allow? Like anything that isn't whitespace or a @, followed by a @, followed by anything that isn't whitespace or a @, followed by a . (dot)`, followed by anything that isn't whitespace or a dot, followed by anything that isn't whitespace?
Over the years I have slowly developed a regular expression that validates MOST email addresses correctly, assuming they don't use an IP address as the server part.
I use it in several PHP programs, and it works most of the time. However, from time to time I get contacted by someone that is hav...
Right now I'm asking what you consider to be a valid email address for your purposes, more than about what the specific parts of the regex are trying to do.
(The top answer to that question should clarify why I am unsure what you actually mean by "email address" for this purpose. A regex that really matches all valid email addresses is extremely long and complicated, and your program might or might not really be able to use any such email address after allowing it.)
I have this function to validate an email addresses:
function validateEMAIL($EMAIL) {
$v = "/[a-zA-Z0-9_-.+]+@[a-zA-Z0-9-]+.[a-zA-Z]+/";
return (bool)preg_match($v, $EMAIL);
}
Is this okay for checking if the email address is valid or not?
well i just wanted to confirm terdons statement, not using php gain ;) i stepped away from php long time ago
stil finding my way in php but i switched to python nearly completely for most things
simply seems the parser of that plugin cant understand ereg compliant regex, and i doubt its really worth relearning since it seems when it comes to file operations and so on this regex type wont help me
just would have been nice to confirm terdons statement
The ereg functions use POSIX ERE, so I think you can test the regex with grep -E, though GNU Grep will support some things as GNU extensions that POSIX ERE does not support.
Is it possible that the regex text you are now trying is actually corrupted and different from what you used in the codebase that appears to be working?
It could be an artifact/bug associated with chat, or maybe even a bug Firefox on my end, I suppose. But I'd definitely look into that. All the characters in it should be representable as ASCII, so I don't know why not using UTF-8 would actually be a problem. Can you provide the regex in some other way than chat? Like in a gist or pastebin or something?
Or if the PHP code is public, you could link to the repo. (I don't know if it is though.)
Well... assuming I understand correctly that PHP ereg is POSIX ERE, you should actually be able to test it with other dialects that support all the POSIX ERE features you're using. With the exception of, like, whether ^ and $ match newlines inside a string, or whether . matches weird whitespace, or exactly what is considered to be in the ranges A-Z and a-z other than the usual 26 capital and lower case letters, other dialects should use your regex the same way.
You might try it with Rubular. That's my favorite online one, even though it doesn't support numerous dialects like RegexBuddy.
Anyway, I didn't have to actually finish writing or run a PHP program to figure out what was going wrong for me originally. So I'm pretty happy about that! :) :) :)
@Videonauth Well, regexbuddy.com/wine.html, but I imagine you mean something that runs natively on Ubuntu without Wine?
I asked for recommendations for Regex editors on stackoverflow a while ago.
Following is one of the replies:
What is "good" depends on what is most
useful to you. For me, though, these
are the key features for a good regex
editor (besides the ability to test
and create regular expres...
Anyway, I haven't tested the specifics of what he said, but terdon is correct that there are many email addresses, that one is even likely actually to encounter, that the regex you showed does not match. For example, it matches abc@xyz.com but not abc@xy.com, and there are many two-letter domains in use, e.g., bp.com.
well i dont know then why i inflicted that limit, i know nowadays you can get a two letter domain easily, back then i was doing webhosting and i had all two letter domains rejected from registering
So you had said you have been learning Python. I hope my "dare" doesn't put you off of that or anything, it's just for fun. I'm also curious -- was your first programming language a shell language?
I hear people saying that learning shell scripting first is easy or a good idea, etc., but I don't know if I've met anybody who actually did it, nor is it at all clear to me that there is any good reason to learn shell scripting first. So I'm curious.
The only language I know how to write any code in at all is Bash (unless sed counts), and I don't know much of that. I won't be put off trying to learn Python, I just hope I will be more conscientious about doing so than I am right now :)
So, not having learned other languages before Bash, when you write Bash scripts, are you not constantly filled with a feeling that shell scripting is super weird?
Because I constantly feel that way.
I am not sure I have asked that question very well.
I do not know of any good informal way to reason about what a shell command means. People sometimes say that shell scripting is easy to learn but I have never understood why they think so. In a so-called "real programming language" like C or Python, the language's structure is conceptually similar to natural language in a way that shell scripting is not.
If natural language used parameter expansion, then understanding the sentence, "Feed the dog," would entail replacing "the dog" with the actual dog it represents and putting that actual dog into sentence. That's impossible because in life we talk about things besides text; conversations can be about things other than themselves.
I don't feel that shell scripting is weird, but I usually feel amused and delighted when I try to understand or do something in other languages, because it seems so clear and simple. But sometimes it also seems very laborious, like an overly long explanation
>>> import re
>>> r = re.compile('(?i)lsb')
>>> with open('/var/log/boot.log', 'r') as f:
... for line in f:
... if r.search(line):
... print(line, end='')
...
[ OK ] Started LSB: AppArmor initialization.
Starting LSB: daemon to balance interrupts for SMP systems...
Starting LSB: Record successful boot for GRUB...
Starting LSB: automatic crash report generation...
Starting LSB: loads/unloads the sep3_15 driver at boot/shutdown time...
In case you are wondering, I'm kidding. Even simple code like that is quite laborious compared to using the shell. (Though the second one is sort of reverse-cheating since I could call grep from Python.)
I have this function to validate an email addresses:
function validateEMAIL($EMAIL) {
$v = "/[a-zA-Z0-9_-.+]+@[a-zA-Z0-9-]+.[a-zA-Z]+/";
return (bool)preg_match($v, $EMAIL);
}
Is this okay for checking if the email address is valid or not?
I asked for recommendations for Regex editors on stackoverflow a while ago.
Following is one of the replies:
What is "good" depends on what is most
useful to you. For me, though, these
are the key features for a good regex
editor (besides the ability to test
and create regular expres...
