Stories
Slash Boxes
Comments

NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

Devel::EnforceEncapsulation headed to CPAN More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Changing my mind (Score:2)

by Ovid (2709) on 2006.10.09 17:36 (#50912) Homepage Journal

After giving it a lot of thought, I'm thinking now that Class::Encapsulate might seem like a good idea, but it's probably more trouble than it's worth. I think that your plan of applying it at runtime for development is probably a cleaner way to go.

Reply to This
- Re: (Score:1)
  
  by ChrisDolan (2855)
  
  I appreciate that. In our discussions, I've been frequently reminded of Linus Torvalds' opinion [lwn.net] on hacks to protect the Linux userspace from stack smashing exploits:
  "In short, anybody who thinks that the non-executable stack gives them any real security is very very much living in a dream world. It may catch a few attacks for old binaries that have security problems, but the basic problem is that the binaries allow you to overwrite their stacks."
  In typical Linus style that statement is harsher than it need

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.