That diotalevi was able to whip that patch up in 1/2 hour indicates that "obfuscation" by variable renaming is not useful at all. One could create a similar patch that renames those variables back. Eg I select a piece of code which contains an interesting algorithm (do you really think anyone would care to reverse engineer a whole software package?), and first replace the variables with var1...varN. Then, as I grasp the meaning, I replace the names one by one by something sensible. It's really not much effort. That is, if you have the time to do an easter-egg hunt for bugs/special features in other people's code.
By the way, why are you still staying anonymous? You are expressing strong opinions, which is perfectly alright, but it would be easier to take you more seriously if one could associate a name with the posts.
Also, in what way are you affiliated with stunnix.com?
-
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.
|