[wp-hackers] meenews: obfuscated code

Iain Cambridge wackiebackie at gmail.com
Thu Nov 25 10:08:16 UTC 2010


>I think Ralf (from the subject) and Ncolas (from the quote above) are trying
>to say the code looks obfuscated and is thus not compliant.
>
>However, I think that the author just got the line endings screwed.
>If you search and replace {four or more spaces} with <newline>+{those
>spaces}, the files look quite normal, not even vaguely obfuscated.

Ah forgot about the title and that one word makes everything else make
sense. Cheers. Yea I have to agree that code isn't obfuscated.

>I don't think so, if there is no licence, copyright applies.
>There is no occurrence of licence in the code, headers, nor in the readme.
>
>The only reference of (L)GPL are those of the libraries :
>ui.tabs.js, colorpicker.js, class.smtp.php, colorpicker.js, class.phpmailer.php, jquery.validate.min.js
>AFAIK, those with a pure-GPL licence can not be used by non free code.

>The code is non-free :
>http://www.gnu.org/copyleft/gpl.html#section1

If you look at http://wordpress.org/extend/plugins/about/ You will see
clause 5 of the requirements being if no license is specified it is
GPLv2.

You are claiming that because it doesn't fill your preference of how
source code should be laid out, it's non-free? Well using that logic
code that has { } on separate lines is non-free because it's not my
preference to have it laid out. Since I am not a lawyer I am not sure
but not having new lines in your code doesn't seem like a GPL breaker
and the line you seem to be focused on seems to be explanatory and not
a clause.


More information about the wp-hackers mailing list