[Autogenerated] And breathe.
The real importance of these summaries is to give you time to
think and just evaluate what we've looked at.
And I'm hoping you're going to agree that we've been through an
absolutely awesome module with really practical features that you're
going to be able to implement very soon.
We've taken a look at how we can use arc to translate
files to different file formats.
We started off with our E T C password file and seeing
how we can get CS V data from it.
So instead of the colon separated file,
we were working with the commerce separated values for this,
we needed to work with our O F S variable,
our output field separator, which is normally going to be a space,
but we're changing it to a comma to be able to see that though.
We have to make sure that we've got commas between
the fields in our print statement.
Now, this is nothing to do with our O F S but just syntax that we need for print.
So it doesn't matter which O F S we want to use,
we separate the arguments to print with a comma and we said,
if we don't set, the O F S, the default value is in fact a space.
But again,
we could still use our print dollar one comma dollar three to
have space separated entries being printed.
We moved on to YAML.
Then YAML is one of our data manipulation languages that source
our data out and makes it easy to edit and easy to read because
it doesn't deal with syntax elements, its white space sensitive.
So instead of having blocks of code being set up,
let's say with brace brackets, we have indents setting our blocks,
but the indentation must be done with spaces and not with tabs.
We also looked within our arc file when we were working with this,
how we can implement more complex statements within arc
using four loops and switch statements, all of which have their own blocks.
But the more normal blocks we are used to with the brace brackets,
we've finished up by looking at tag data.
So XML style data that we might have within our Apache configuration files,
we were seeing there that we could use then the R S variable,
our record separator now that normally would be a new line,
but we were saying that we wanted it to be two new lines.
So we might obviously think slash end slash N for two new lines,
but of course, slash end is just escaping the end.
So we need to go back slash back slash N and to be
certain that it is going to work.
We can also put a slash s for any white space character following
the new line or between the new two new lines.
So here we've got our slash ss an asterisk saying any amount of white space.
But of course, again, it needs to be a double back slash.
So the back slash is read as a literal back slash.
The importance of having our data correct in the first instance.
And we saw that by editing the file,
we could remove any additional white space that we didn't want the blank
lines and add in a blank line between each of our records.
This way,
we've got data that we understand the format of and we're then
going to be able to get accurate results coming out.
Now, I do hope you agree with me and do feel this has been really, really good.
You might want to go back and look at some of the
modules that we've seen within this,
but do go over them and do practice them with your own set up.
But if you're ready to move on and by,
have we got something good for you coming up looking
at filtering data from log files.