Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

splitting with a regex & keeping a ref?

13 views
Skip to first unread message

Kyle Schmitt

unread,
May 1, 2008, 10:46:38 AM5/1/08
to
I'm writing some scripts to help handle some ornery samba servers we
have: part of that is unfortunately reading the config scripts that
have built up over the years.

I was hoping to use the standard string method as a quick &
not-so-dirty way of parsing the files, given that samba uses a very
simple format.

#the sample_data variable is defined below
irb(main):sample_data.split(/\[[a-z0-9]+\]/i)
=> ["", "\ncomment = shared directory for the shop\npath =
/dept/shop\nvalid u ....(truncated)
Gives good results, but omits what's between the brackets. I expected
that part.

irb(main):sample_data.split(/(\[[a-z0-9]+\])/i)
=> ["", "[shop]", "\ncomment = shared directory for the shop\npath =
/dept/sho ....(truncated)
Neat, gives me the data between the brackets in an element before the
data itself.


I know quite well I can zip through that array again, but I was
wondering, hoping, that there would be a way of accessing that back
reference in a block as part of the split.

Is there any way to do that that I'm just missing?

Thanks,
Kyle

sample_data=%{[shop]
comment = shared directory for the shop
path = /dept/shop
valid users = @shop @admin
public = no
writable = yes
force group = shop
create mask = 0770
[bob]
comment = User files for bob
path = /users/bob
valid users = bob @admin
public = no
writable = yes
create mask = 0770}

David A. Black

unread,
May 1, 2008, 10:55:20 AM5/1/08
to
Hi --

On Thu, 1 May 2008, Kyle Schmitt wrote:

> I'm writing some scripts to help handle some ornery samba servers we
> have: part of that is unfortunately reading the config scripts that
> have built up over the years.
>
> I was hoping to use the standard string method as a quick &
> not-so-dirty way of parsing the files, given that samba uses a very
> simple format.
>
> #the sample_data variable is defined below
> irb(main):sample_data.split(/\[[a-z0-9]+\]/i)
> => ["", "\ncomment = shared directory for the shop\npath =
> /dept/shop\nvalid u ....(truncated)
> Gives good results, but omits what's between the brackets. I expected
> that part.
>
> irb(main):sample_data.split(/(\[[a-z0-9]+\])/i)
> => ["", "[shop]", "\ncomment = shared directory for the shop\npath =
> /dept/sho ....(truncated)
> Neat, gives me the data between the brackets in an element before the
> data itself.
>
>
> I know quite well I can zip through that array again, but I was
> wondering, hoping, that there would be a way of accessing that back
> reference in a block as part of the split.

I'm afraid I can't quite follow that sentence. What do you mean by a
back reference? Can you show some sample desired output?


David

--
Rails training from David A. Black and Ruby Power and Light:
INTRO TO RAILS June 9-12 Berlin
ADVANCING WITH RAILS June 16-19 Berlin
INTRO TO RAILS June 24-27 London (Skills Matter)
See http://www.rubypal.com for details and updates!

Kyle Schmitt

unread,
May 1, 2008, 11:13:27 AM5/1/08
to
David, back reference as in a regex back reference.
In a nutshell, it stores what was matched, and allows you to do
something with it. You just place parentheses around the part of the
match you want to save.

They work like this in ruby's gsub (but a little differently in sed,
if that's the regex you grew up with).

example=%{Brian had a dog
James had a cat
Allen has a hampster}
puts example
#If you wanted to change the type of pet with gsub, you could do it like this...
puts example.gsub("/[^ ]+$/","grue")
#but if you wanted to describe the pet, and not change the type, you'd
need a backreference
puts example.gsub(/([^ ]+$)/){|i| "big ugly #{i}"}

Kyle Schmitt

unread,
May 1, 2008, 11:17:38 AM5/1/08
to
Ohh right, desired sample output.

What I'd really like, is to split the string, and either stuff it
straight into a hash at the same time, or, more realistically since
it's splitting, array tuples.
So...

sample.data.split(){magic happens here}
=>{"[shop]"=>"\ncomment = shared directory for the shop\npath..>"}

or
sample.data.split(){magick happens here}
=>[["[shop]","\ncomment = shared directory for the shop\npath..>"]]

Kyle Schmitt

unread,
May 1, 2008, 11:44:29 AM5/1/08
to
David,
re-reading your sig, and that page, I've got to apologize,
you already knew that stuff in spades I'm sure! :)

What part doesn't quite make sense?

yermej

unread,
May 1, 2008, 12:08:41 PM5/1/08
to

I think you might want scan instead of split.

sample_data.scan( /(\[[a-z0-9]+\])([^\[]*)/i) do |share, opts|
# create your hash or whatever here
end

Kyle Schmitt

unread,
May 1, 2008, 12:24:31 PM5/1/08
to
yermej,
scan you say. Heh, I never even thought of that one.
Makes the whole thing rather simple!

Thanks.

Robert Klemme

unread,
May 1, 2008, 12:29:45 PM5/1/08
to

Yes. Two suggestions:

robert@fussel /cygdrive/c/Temp
$ ./smpars.rb
{"shop"=>
{"public"=>"no",
"writable"=>"yes",
"create mask"=>"0770",
"valid users"=>"@shop @admin",
"path"=>"/dept/shop",
"comment"=>"shared directory for the shop",
"force group"=>"shop"},
"bob"=>
{"public"=>"no",
"writable"=>"yes",
"create mask"=>"0770",
"valid users"=>"bob @admin",
"path"=>"/users/bob",


"comment"=>"User files for bob"}}

{"shop"=>
{"public"=>"no",
"writable"=>"yes",
"create mask"=>"0770",
"valid users"=>"@shop @admin",
"path"=>"/dept/shop",
"comment"=>"shared directory for the shop",
"force group"=>"shop"},
"bob"=>
{"public"=>"no",
"writable"=>"yes",
"create mask"=>"0770",
"valid users"=>"bob @admin",
"path"=>"/users/bob",


"comment"=>"User files for bob"}}

robert@fussel /cygdrive/c/Temp
$ cat smpars.rb
#!/bin/env ruby

require 'pp'

sample_data = <<EOS


[shop]
comment = shared directory for the shop
path = /dept/shop
valid users = @shop @admin
public = no
writable = yes
force group = shop
create mask = 0770
[bob]
comment = User files for bob
path = /users/bob
valid users = bob @admin
public = no
writable = yes
create mask = 0770

EOS

def parse1(dat)
conf = {}
key = nil
dat.each do |line|
case line
when /^\s*\[([^\]]+)\]\s*$/
key = $1
conf[key] ||= {}
when /^\s*([^=]*?)\s*=\s*(.*)$/
conf[key][$1] = $2
end
end
conf
end

def parse2(dat)
conf = {}
key = nil
dat.scan %r{
^\s*\[([^\]]+)\]\s*$
| ^\s*([^=]*?)\s*=\s*(.*)$
}x do |m|
if m[0]
key = m[0]
conf[key] ||= {}
else
conf[key][m[1]] = m[2]
end
end
conf
end

pp parse1(sample_data)
pp parse2(sample_data)

robert@fussel /cygdrive/c/Temp
$

Cheers

robert

Kyle Schmitt

unread,
May 1, 2008, 12:54:33 PM5/1/08
to
Robbert, yermej, David,

Thanks a bunch!
Here's what I finally came up with, in case anyone's bored enough to wonder.

file="/path/to/smb/file/sample.conf"
regex=/(\[[a-z0-9]+\])([^\[]*)/i
samba_config={}
File.open(file){|f| f.read()}.scan(regex) do
|title,options|
samba_config.store(title,{})
options.strip.each() do
|l|
samba_config[title].store(l[/^[^=]*/].strip,l[/[^=]*[^\n]$/].strip)
end
end

David A. Black

unread,
May 1, 2008, 1:31:24 PM5/1/08
to
Hi --

I know you're not asking for refactoring advice, but here's some
anyway :-)

If you're just going to read a file's contents into a string, you can
use File.read, rather than the whole open/read thing. Also, I'd
encourage you to drop the empty parentheses after method names. The
message-sending dot tells you that it's a method; the () doesn't add
signal, just noise.

Anyway, here's a tweaked version, in case it's of interest. Nothing
too radical, just a couple of possibly fun alternative techniques :-)

File.read("filename").scan(regex) do |title,options|
samba_config[title] = {}
options.strip.each do |option|
samba_config[title].update(Hash[*option.strip.split(/\s*=\s*/)])
end
end

Kyle Schmitt

unread,
May 1, 2008, 2:46:09 PM5/1/08
to
David,
I don't mind it at all!

Out of curiosity, agreeing that File.read().scan() is much cleaner, is
it just syntactic sugar for the same thing, or is it computationally
different?

Thanks for the Hash[*Array] syntax btw, I've used it way way back, but
for the life of me couldn't remember it, thought maybe I was mistaken.

David A. Black

unread,
May 1, 2008, 4:16:17 PM5/1/08
to
Hi --

On Fri, 2 May 2008, Kyle Schmitt wrote:

> David,
> I don't mind it at all!
>
> Out of curiosity, agreeing that File.read().scan() is much cleaner, is
> it just syntactic sugar for the same thing, or is it computationally
> different?

I don't know whether File.read is actually written in terms of
File.open (I'm afraid I'm too lazy to check right now), but I think
the underlying system calls etc. would be at least very similar. I
expect File.read is slightly cheaper, since it doesn't involve the
whole block structure. (I'm talking, of course, specifically about
comparison with File.open {|f| f.read }, where you get the whole file
at once.)

William James

unread,
May 1, 2008, 10:48:17 PM5/1/08
to
On May 1, 9:46 am, Kyle Schmitt <kyleaschm...@gmail.com> wrote:

regex = /(\[.*?\])/
h = Hash[ *IO.read("data").strip.split( regex )[1..-1] ]
h.each{|k,v| h[k] = Hash[ *v.strip.split( / *= *|\n/ ) ] }

0 new messages