The (*) notation was going to be a quick and dirty reference to a non-inherited permission for a file. I didn't mention it in the initial posting, but mentioned it in the posting where I show it between the CSV in and CSV out samples.

The columns show:
File Server,Access Path,Current Permissions,Logon Name,Inherited From Folders,Flags,User/Group,Classification Results,Classification Results by Category (Including Nested),Total Hit Count

In the sample input CSV, there are a few unique files shown(column 2), and column 3 shows what permissions each user or group has to that file. So those get minimized to show 1 line per file, and it's column 4 where I start packing all the users and groups together that all have the same permissions seen in column 3.

There's no order to the combine list of users/groups. As I'm parsing the file (sorted by server and filename and permissions), I intend to look at whether those are all the same, and if there's a user already associated with that permission for that file, I append the current line's user onto the list of users that are already having the same permissions. So it's just "whatever comes next" for the list of users.

I'm sorry I didn't that more clear.

I'm going to pore over what people have submitted because I have a lot to learn from those techniques. I do want to thank everyone who has provided sample code! I had training all day today, and will have another day tomorrow, and I'll look more closely at it.

I saw someone used map above, and I failed in using it, and couldn't figure out why it failed, so I want to look over how it's being used there. I could only use it on @ARGV for some reason, and not other arrays. (I had a comment in my code that mentioned the failure)

Thank you again! I'll be sure to ask some questions if I can't figure out how some of the code functionality works.

In reply to Re^2: Building a dynamic array or some other method? by CAdood
in thread Building a dynamic array or some other method? by CAdood

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.