This document discusses advanced concepts of regular expressions in Ruby, emphasizing the various functions and features such as match data, lookarounds, and different types of quantifiers. It illustrates how to manipulate strings and extract information using Ruby's regex capabilities, detailing both greedy and lazy behaviors, as well as the use of positive and negative assertions. The presentation encourages users to practice writing regex by breaking them down into manageable parts.

1. BEYOND THE BASICS
Regular Expressions in Ruby
@nellshamrell
Thursday, February 7, 13

2. ^4[0-9]{12}(?:[0-9]{3})?$
Source: regular-expressions.info
Thursday, February 7, 13

3. Regular Expressions are Patterns
Thursday, February 7, 13

4. Test
Extract
Change
Thursday, February 7, 13

5. Test
Extract
Change
Thursday, February 7, 13

6. Test
Extract
Change
Thursday, February 7, 13

7. In Ruby, regular
expressions are objects
Thursday, February 7, 13

8. You program from a regular
expression to a result
Source: The Well Grounded Rubyist
Thursday, February 7, 13

9. Oniguruma
Thursday, February 7, 13

10. Shorthand for Hexadecimals
/h and /H
Thursday, February 7, 13

11. Onigmo
Thursday, February 7, 13

12. Thursday, February 7, 13

13. =~
Thursday, February 7, 13

14. /force/ =~ “Use the force”
Thursday, February 7, 13

15. “Use the force” =~ /force/
Thursday, February 7, 13

16. “Use the force” =~ /force/
=> 8
Thursday, February 7, 13

17. /dark side/ !~ “Use the force”
Thursday, February 7, 13

18. /dark side/ !~ “Use the force”
=> true
Thursday, February 7, 13

19. MatchData
Thursday, February 7, 13

20. .match
Thursday, February 7, 13

21. string = “The force will be with
you always.”
Thursday, February 7, 13

22. string = “The force will be with
you always.”
m =/force/.match(string)
Thursday, February 7, 13

23. string = “The force will be with
you always.”
m =/force/.match(string)
=> #<MatchData “force” >
Thursday, February 7, 13

24. string = “The force will be with
you always.”
m =/force/.match(string,5)
Thursday, February 7, 13

25. string = “The force will be with
you always.”
m =/force/.match(string,5)
=> nil
Thursday, February 7, 13

26. What can you do with MatchData?
Thursday, February 7, 13

27. m.to_s
Thursday, February 7, 13

28. m.to_s
=> “force”
Thursday, February 7, 13

29. m.to_s
=> “force”
m.pre_match
Thursday, February 7, 13

30. m.to_s
=> “force”
m.pre_match
=> “The ”
Thursday, February 7, 13

31. m.to_s
=> “force”
m.pre_match
=> “The ”
m.post_match
Thursday, February 7, 13

32. m.to_s
=> “force”
m.pre_match
=> “The ”
m.post_match
=> “ be with you”
Thursday, February 7, 13

33. Capture Groups
Thursday, February 7, 13

34. /(.*)force(.*)/
Thursday, February 7, 13

35. m = /(.*)force(.*)/.match(string)
Thursday, February 7, 13

36. m = /(.*)force(.*)/.match(string)
m.captures
Thursday, February 7, 13

37. m = /(.*)force(.*)/.match(string)
m.captures
=> [“The ”,
“will be with you always”]
Thursday, February 7, 13

38. You access capture groups with []
Thursday, February 7, 13

39. m[1]
Thursday, February 7, 13

40. m[1]
=> “The ”
Thursday, February 7, 13

41. m[1]
=> “The ”
m[2]
Thursday, February 7, 13

42. m[1]
=> “The ”
m[2]
=> “ will be with you always ”
Thursday, February 7, 13

43. m[0]
Thursday, February 7, 13

44. m[0]
=> “The force will be with
you always.”
Thursday, February 7, 13

45. Match Objects are not arrays
Thursday, February 7, 13

46. m.each do |match|
puts match.upcase
end
Thursday, February 7, 13

47. m.each do |match|
puts match.upcase
end
=> NoMethodError
Thursday, February 7, 13

48. m.to_a.each do |match|
puts match.upcase
end
Thursday, February 7, 13

49. m.to_a.each do |match|
puts match.upcase
end
=> “THE FORCE WILL BE
WITH YOU ALWAYS”
“THE ”
“WILL BE WITH YOU
ALWAYS”
Thursday, February 7, 13

50. Thursday, February 7, 13

51. LookArounds Define Context
Thursday, February 7, 13

52. string = “Who’s the more
foolish? The fool or
the fool who follows
him?”
Thursday, February 7, 13

53. string = “Who’s the more
foolish? The fool or
the fool who follows
him?”
/fool/
Thursday, February 7, 13

54. string.scan(/fool/)
Thursday, February 7, 13

55. string.scan(/fool/)
=> [“fool”, “fool”, “fool”]
Thursday, February 7, 13

56. Positive Lookahead
Thursday, February 7, 13

57. ?=
Thursday, February 7, 13

58. string.scan(/fool(?=ish)/)
Thursday, February 7, 13

59. string.scan(/fool(?=ish)/)
=> [“fool”]
Thursday, February 7, 13

60. string.gsub(/fool(?=ish)/, “self”)
Thursday, February 7, 13

61. string.gsub(/fool(?=ish)/, “self”)
=> “Who’s the more
selfish? The fool or
the fool who follows
him?”
Thursday, February 7, 13

62. Zero Width Positive
Lookahead Assertion
Thursday, February 7, 13

63. Zero width means it does not
consume characters
Thursday, February 7, 13

64. Positive means a match for the
lookahead should be present
Thursday, February 7, 13

65. Lookahead means it is looking
ahead of your main match.
Thursday, February 7, 13

66. Assertion means the lookahead only
determines whether a match exists
Thursday, February 7, 13

67. string = “Who’s the more
foolish? The fool or
the fool who follows
him?”
Thursday, February 7, 13

68. Negative Lookahead
Thursday, February 7, 13

69. Negative means a match for the
lookahead should not be present
Thursday, February 7, 13

70. ?!
Thursday, February 7, 13

71. string.scan(/fool(?!ish)/)
Thursday, February 7, 13

72. string.scan(/fool(?!ish)/)
=> [“fool”, “fool”]
Thursday, February 7, 13

73. string.gsub(/fool(?!ish)/, “self”)
Thursday, February 7, 13

74. string.gsub(/fool(?!ish)/, “self”)
=> “Who’s the more
foolish? The self or
the self who follows
him?”
Thursday, February 7, 13

75. Positive Lookbehind
Thursday, February 7, 13

76. string = “For my ally is the
force, and a powerful
ally it is”
Thursday, February 7, 13

77. string = “For my ally is the
force, and a powerful
ally it is”
/ally/
Thursday, February 7, 13

78. ?<=
Thursday, February 7, 13

79. /(?<=powerful )ally/
Thursday, February 7, 13

80. string.gsub(/(?<=powerful )ally/,
“friend”)
Thursday, February 7, 13

81. string.gsub(/(?<=powerful )ally/,
“friend”)
=> “For my ally is the
force, and a powerful
friend it is”
Thursday, February 7, 13

82. Negative Lookbehind
Thursday, February 7, 13

83. ?<!
Thursday, February 7, 13

84. /(?<!powerful )ally/
Thursday, February 7, 13

85. string.gsub(/(?<!powerful )ally/,
“friend”)
Thursday, February 7, 13

86. string.gsub(/(?<!powerful )ally/,
“friend”)
=> “For my friend is the
force, and a powerful
ally it is”
Thursday, February 7, 13

87. Thursday, February 7, 13

88. Regular Expressions have
distinct behaviors
Thursday, February 7, 13

89. Greedy
Lazy
Possessive
Thursday, February 7, 13

90. Greedy
Lazy
Possessive
Thursday, February 7, 13

91. Greedy
Lazy
Possessive
Thursday, February 7, 13

92. Quantifiers
Thursday, February 7, 13

93. +
Thursday, February 7, 13

94. +
/.+/
Thursday, February 7, 13

95. Quantifiers are greedy by default
Thursday, February 7, 13

96. Greedy Quantifiers match
as much as possible
Thursday, February 7, 13

97. Greedy Quantifiers use maximum
effort for maximum return
Thursday, February 7, 13

98. string = “This is no time to
talk about time we
don’t have the time”
Thursday, February 7, 13

99. string = “This is no time to
talk about time we
don’t have the time”
/.+time/
Thursday, February 7, 13

100. /.+time/.match(string)
Thursday, February 7, 13

101. /.+time/.match(string)
=> “This is no time to
talk about time we
don’t have the time”
Thursday, February 7, 13

102. Greedy regular expressions
try to match the whole
string, then backtrack
Thursday, February 7, 13

103. Oniguruma makes
backtracking quicker
Thursday, February 7, 13

104. Lazy Quantifiers
Thursday, February 7, 13

105. Lazy Quantifiers match
as little as possible
Thursday, February 7, 13

106. Lazy Quantifiers use minimum
effort for minimum return
Thursday, February 7, 13

107. /.+?time/
Thursday, February 7, 13

108. /.+?time/.match(string)
Thursday, February 7, 13

109. /.+?time/.match(string)
=> “This is no time”
Thursday, February 7, 13

110. Lazy regular expressions
use less resources
Thursday, February 7, 13

111. Possessive Quantifiers
Thursday, February 7, 13

112. Possessive Quantifiers are
all or nothing
Thursday, February 7, 13

113. Possessive Quantifiers try to
match the entire string
with no backtracking
Thursday, February 7, 13

114. Possessive Quantifiers use
minimum effort for
maximum return
Thursday, February 7, 13

115. /.++time/
Thursday, February 7, 13

116. /.++time/.match(string)
Thursday, February 7, 13

117. /.++time/.match(string)
=> nil
Thursday, February 7, 13

118. Possessive Quantifiers
fail faster
Thursday, February 7, 13

119. Thursday, February 7, 13

120. Write regular expressions
in small chunks
Thursday, February 7, 13

121. Rubular
Thursday, February 7, 13

122. Regular expressions come in drafts
Thursday, February 7, 13

123. Move beyond your fear
of regular expressions
Thursday, February 7, 13

124. Nell Shamrell
Software Development Engineer
Blue Box Group
@nellshamrell
Thursday, February 7, 13