comment on

Wait! The language can't be safely syntax checked, and thus can't be safely debugged, either, right? (Any hostile code won't be intercepted until after the initial syntax check, by which time it's too late.)

Can you explain to me how a syntax check can detect hostile code? Your whole premise seems to depend on this and I can't see how it relates...

If the syntax check fails, then I would assume that the code will not execute (you will get a compiler error)! And if the syntax check passes, all that tells you is that the program will execute without a compiler error. Nowhere would it say 'Syntax check failed because of hostile code'. So what does a syntax checker gain you here in added safety?

I'm just a little confused about what you are actually trying to accomplish here...

ps I did read all the posts in the thread, but I may have missed something. Appologies if I did...

In reply to Re^2: Perl Will Stay a Dynamic Language by cees
in thread Syntax checking without BEGIN blocks by Anonymous Monk

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


No such thing as a small change
	PerlMonks