Outside of non-professional teenage Slashdot readers who still think the shitty Perl syntax is 'kewl', who the hell cares about the language anymore?
Perhaps people who want to work for the dozens of Fortune 500 companies who have huge numbers of systems written in Perl. Or perhaps people who want to work for the large number of internet startups that use a lot of Perl code.
But, hey, if neither of those options really appeal to you then feel free to use something else. The fewer people that want to write Perl, the more I get paid for writing it.
Actually the first series was six episodes, then there was a one-off special and the second series was five parts. The special is usually included as part of the the second series.
Then, of course, there is the the six-part third series.
how did you know it would be in the first 250 digits?
I didn't. That was just a prototype. I was planning to replace the assignment with an interator that generated the digits of e. I was pretty surprised when it came up with the right answer.
There is no way to do what you want. Any reasonable Perl programmer can undo Stunnix obfuscation in minutes. All that's left is the strange variable names.
By all means use it if you want. But don't expect it to give you any protection from people reading your source code.
Re:Let's reinvent the wheel again
on
XML and Perl
·
· Score: 1
Although I agree that Perl/XML sounds like a powerful and flexible way to serve dynamic content,
You need to move on from thinking that everything is there purely to be used for the web. Well over half of the work I've done with XML and Perl has nothing to do with the web.
Let me let you into a little secret. Reviewers don't buy books. Publishers send us free copies.
I would have to also ask if there was any coverage of SAMBA
Yep. Chapter 18 is all about setting up a Linux file server and it includes 16 pages on configuring SAMBA. Much of that is about confuguring it using SWAT.
Slashdot Mirror
Perhaps people who want to work for the dozens of Fortune 500 companies who have huge numbers of systems written in Perl. Or perhaps people who want to work for the large number of internet startups that use a lot of Perl code.
But, hey, if neither of those options really appeal to you then feel free to use something else. The fewer people that want to write Perl, the more I get paid for writing it.
Show a creationist a transitional fossil and he'll just see two gaps instead of one.
Actually the piece was in the Technology supplement of Thursday's Guardian newpaper. The Observer is a Sunday paper.
Dave...
Exactly. And that's what warn does. It prints to STDERR.
Actually the first series was six episodes, then there was a one-off special and the second series was five parts. The special is usually included as part of the the second series.
Then, of course, there is the the six-part third series.
There are no towels in the film :(
The first radio series is six half hour episodes - that's three hours.
I didn't. That was just a prototype. I was planning to replace the assignment with an interator that generated the digits of e. I was pretty surprised when it came up with the right answer.
You don't need to know that. Here's how I solved it when I first heard about it in July.
Er... no. Learning Perl is a tutorial, Programming Perl is a reference. There's a huge difference.
You've not seen B::Deobfuscate yet then :)
This is covered in the Perl FAQ.
How can I hide the source for my Perl program?
There is no way to do what you want. Any reasonable Perl programmer can undo Stunnix obfuscation in minutes. All that's left is the strange variable names.
By all means use it if you want. But don't expect it to give you any protection from people reading your source code.
Please don't expect Stunnix to give you any level of security. You should read the discussion on Perlmonks.
No you don't. This is the first edition of Programming Web Services with Perl . Looks like you have a copy of Programming Web Services with SOAP . Two completely separate books with a small amount of overlap.
You need to move on from thinking that everything is there purely to be used for the web. Well over half of the work I've done with XML and Perl has nothing to do with the web.
Let me let you into a little secret. Reviewers don't buy books. Publishers send us free copies.
Yep. Chapter 18 is all about setting up a Linux file server and it includes 16 pages on configuring SAMBA. Much of that is about confuguring it using SWAT.
Sorry, no. My review copy was given to me earlier this month by the nice people at Diverse Books.
It's partly my fault. I got my review copy in June :-/
Not sure what you're trying to imply here. I have nothing at all to do with the publisher.
No. It was released today. You're thinking of the last Release Candidate which was released on Monday.
That's very cool. I'd love to hear more details of how my book saved your comapny that much money.
Yeah, that's covered in great depth the section on security that I mentioned in the review.
Oh, nothing. It's just that I would rather not have had it presented as the only templating solution.
I don't see anyone claiming that it's a good idea. Simply that it's something that can be done (and therefore was).