Re^2: IF and GREP Question

That will not work because the NB_FILE handle will exhaust the records in the first loop.

Depending on how many records you expect, you may need to save the contents of the file in an array, to avoid the I/O overhead.

If that is not viable, read the file, record-at-a-time in a loop, then loop through @backup_jobs for each record.

My goal ... to kill off the slow brain cells that are holding me back from synergizing my knowledge of vertically integrated mobile platforms in local cloud-based content management system datafication.

Comment on Re^2: IF and GREP Question

Replies are listed 'Best First'.
Re^3: IF and GREP Question by kcott (Archbishop) on Sep 18, 2013 at 05:33 UTC
"That will not work because the NB_FILE handle will exhaust the records in the first loop." The OP has not provided sufficient information for you to make that statement. I stated what I didn't know as well as the assumptions I had made. For all you or I know, that first "`...`" contains an `open` statement which reuses the `NB_FILE` filehandle. The `for` loop was a stated assumption; perhaps the code doesn't look like that at all; perhaps it's in a subroutine which opens the `NB_FILE` filehandle every time it's called. Anyway, the point is now moot: the OP's subsequent response ("Thank you sir, the code worked great!") rather suggests you're wrong. -- Ken	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^3: IF and GREP Question
by kcott (Archbishop) on Sep 18, 2013 at 05:33 UTC

"That will not work because the NB_FILE handle will exhaust the records in the first loop."

The OP has not provided sufficient information for you to make that statement.

I stated what I didn't know as well as the assumptions I had made.

For all you or I know, that first "..." contains an open statement which reuses the NB_FILE filehandle. The for loop was a stated assumption; perhaps the code doesn't look like that at all; perhaps it's in a subroutine which opens the NB_FILE filehandle every time it's called.

Anyway, the point is now moot: the OP's subsequent response ("Thank you sir, the code worked great!") rather suggests you're wrong.

-- Ken

[reply]
[d/l]
[select]