Re^2: Some automation on Perlscripts?

Thanks for your entertaining reply. Is it right like i seemed to have learned that it is "somewhat complicated" to manipulate files with Perl and Perl is better suited for "manipulating text" so i would use Perl for inserting the text and bash (or anything else) for manipulating file permissions, or i entirely use bash ...? What do you think of using "syscalls" from Perl to start a shell function?

Sorry for asking a no go question ...

I never was aware before that some things you would better not do in (or are even impossible) language "x" but that answers the questions why there are so many languages out there ...

Thanks for sharing your thoughts.
MH

Comment on Re^2: Some automation on Perlscripts?

Replies are listed 'Best First'.
Re^3: Some automation on Perlscripts? by leocharre (Priest) on Dec 04, 2008 at 20:39 UTC
Using syscalls from perl to shell.. From a point of view of getting things done, do it. If you're developing software for release and installating in multiple machines over which you have no control- there's a few things you gotta do extra in your software. Like, checking that the stuff exists, etc. Perl, CPAN, will check great for perl module dependencies. But it's little bit harder for system applications. Purely perl speaking. The things I pointed out, it's not that you should never do it. It's about picking your battles. A system to properly do this, without corrupting data, etc is harder than it sounds. There's a difference between something that looks like it works, and something that does. And then, being on posix, that's part of what the whole thing is about, you use all these things together. Perl, bash, c, whatever. You can manipulate files and set permissions fine with perl. Fletch was cracking a joke. Perl is the answer to the question.	[reply]

Replies are listed 'Best First'.

Re^3: Some automation on Perlscripts?
by leocharre (Priest) on Dec 04, 2008 at 20:39 UTC

Using syscalls from perl to shell..
From a point of view of getting things done, do it.

If you're developing software for release and installating in multiple machines over which you have no control- there's a few things you gotta do extra in your software. Like, checking that the stuff exists, etc.

Perl, CPAN, will check great for perl module dependencies. But it's little bit harder for system applications. Purely perl speaking.

The things I pointed out, it's not that you should never do it. It's about picking your battles.
A system to properly do this, without corrupting data, etc is harder than it sounds.

There's a difference between something that *looks* like it works, and something that does.

And then, being on posix, that's part of what the whole thing is about, you use all these things together. Perl, bash, c, whatever.

You can manipulate files and set permissions fine with perl. Fletch was cracking a joke. Perl is the answer to the question.

[reply]