10-25-2008
Quote:
Originally Posted by
nwboy74
You're not going to be able to use a single regular expression to accomplish that. You might try something like:
if ($str !~ /([a-z]).*\1/ && $str =~ /^[a-z]+$/) {
...
}
I agree, a single regexp would be too complicated, but I think you also just did his school/course work for him.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
For a programming exercise, I am mean to design a Perl script that detects double letters in a text file.
I tried the following expressions
# Check for any double letter within the alphabet
/+/
# Check for any repetition of an alphanumeric character
/\w+/
Im aware that the... (8 Replies)
Discussion started by: JamesGoh
8 Replies
2. Shell Programming and Scripting
I have got numbers like
l255677
l376039
l188144
l340482
l440700
l254113
to match the numbers starting with '13' what would be the regex
=~/13(.*)/ =======>This is not working ....
But for user123,user657
regex =~/user(.*)/ ========>works
Thanks for help..!! (7 Replies)
Discussion started by: trina_1
7 Replies
3. Shell Programming and Scripting
I am having trouble parsing rpm filenames in a shell script.. I found a snippet of perl code that will perform the task but I really don't have time to rewrite the entire script in perl. I cannot for the life of me convert this code into something sed-friendly:
if ($rpm =~ /(*)-(*)-(*)\.(.*)/)... (1 Reply)
Discussion started by: suntzu
1 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I get the following when I cat a file *.log
xxxxx
=====
dasdas gwdgsg fdsagfsag agsdfag
=====
random data
=====
My output should look like :
If the random data after the 2nd ==== is null then OK should be printed else
the random data should be printed.
How do I go about this... (5 Replies)
Discussion started by: manutd
5 Replies
5. Programming
HI,
I'm new to perl and need simple regex for reading a file using my perl script.
The text file reads as -
filename=/pot/uio/current/myremificates.txt
certificates=/pot/uio/current/userdir/conf/user/gamma/settings/security/... (3 Replies)
Discussion started by: jhamaks
3 Replies
6. Programming
Hi Guys
I have the following regex
$OSRELEASE = $1 if ($output =~ /(Mac OS X (Server )?10.\d)/);
output is currently
Mac OS X 10.7.5
when the introduction of Mac 10.8 output changes to
OS X 10.8.2
they have dropped the Mac bit so i changed the regex to be (2 Replies)
Discussion started by: ab52
2 Replies
7. Programming
Hello,
I'm trying to get a quick help on regex since i'm not a regular programmer.
Below is the line i'm trying to apply my regex to..i want to use the regex in a for loop and this line will keep on changing.
subject=... (4 Replies)
Discussion started by: jhamaks
4 Replies
8. Shell Programming and Scripting
Could anyone please make me understand how the ?= works below ..
After executing this I am getting the same output.
$string="I love chocolate.";
$string =~ s/chocolate(?= ice)/vanilla/;
print "$string\n"; (2 Replies)
Discussion started by: scriptscript
2 Replies
9. Shell Programming and Scripting
I am not a big expert in regex and have just little understanding of that language.
Could you help me to understand the regular Perl expression:
^(?!if\b|else\b|while\b|)(?:+?\s+){1,6}(+\s*)\(*\) *?(?:^*;?+){0,10}\{
------
This is regex to select functions from a C/C++ source and defined in... (2 Replies)
Discussion started by: alex_5161
2 Replies
10. Shell Programming and Scripting
Experts -
I found a script on one of the servers that I work on and I need help understanding
one of the lines.
I know what the script does, but I'm having a hard time understanding the grouping.
Can someone help me with this?
Here's the script...
#!/usr/bin/perl
use strict;
use... (2 Replies)
Discussion started by: timj123
2 Replies
LEARN ABOUT CENTOS
perl::critic::policy::regularexpressions::requireextendedformatt
Perl::Critic::Policy::RegularExpressions::RequireExtendeUsermContributed PerPerl::Critic::Policy::RegularExpressions::RequireExtendedFormatting(3)
NAME
Perl::Critic::Policy::RegularExpressions::RequireExtendedFormatting - Always use the "/x" modifier with regular expressions.
AFFILIATION
This Policy is part of the core Perl::Critic distribution.
DESCRIPTION
Extended regular expression formatting allows you mix whitespace and comments into the pattern, thus making them much more readable.
# Match a single-quoted string efficiently...
m{'[^\']*(?:\.[^\']*)*'}; #Huh?
# Same thing with extended format...
m{
' # an opening single quote
[^\'] # any non-special chars (i.e. not backslash or single quote)
(?: # then all of...
\ . # any explicitly backslashed char
[^\']* # followed by an non-special chars
)* # ...repeated zero or more times
' # a closing single quote
}x;
CONFIGURATION
You might find that putting a "/x" on short regular expressions to be excessive. An exception can be made for them by setting
"minimum_regex_length_to_complain_about" to the minimum match length you'll allow without a "/x". The length only counts the regular
expression, not the braces or operators.
[RegularExpressions::RequireExtendedFormatting]
minimum_regex_length_to_complain_about = 5
$num =~ m<(d+)>; # ok, only 5 characters
$num =~ m<d.(d+)>; # not ok, 9 characters
This option defaults to 0.
Because using "/x" on a regex which has whitespace in it can make it harder to read (you have to escape all that innocent whitespace), by
default, you can have a regular expression that only contains whitespace and word characters without the modifier. If you want to restrict
this, turn on the "strict" option.
[RegularExpressions::RequireExtendedFormatting]
strict = 1
$string =~ m/Basset hounds got long ears/; # no longer ok
This option defaults to false.
NOTES
For common regular expressions like e-mail addresses, phone numbers, dates, etc., have a look at the Regexp::Common module. Also, be
cautions about slapping modifier flags onto existing regular expressions, as they can drastically alter their meaning. See
<http://www.perlmonks.org/?node_id=484238> for an interesting discussion on the effects of blindly modifying regular expression flags.
TO DO
Add an exemption for regular expressions that contain "Q" at the front and don't use "E" until the very end, if at all.
AUTHOR
Jeffrey Ryan Thalhammer <jeff@imaginative-software.com>
COPYRIGHT
Copyright (c) 2005-2011 Imaginative Software Systems. All rights reserved.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of this license
can be found in the LICENSE file included with this module.
perl v5.16.3 2014-06-Perl::Critic::Policy::RegularExpressions::RequireExtendedFormatting(3)