![]() |
|
#1
|
|||
|
|||
![]()
Binaries aren't really an issue because this is a perl program. Perl is interpreted (or, stricly speaking, run-time compiled). The source code is the program, and you need the perl interpreter on your machine to run it.
Definitions for non-programmers: Compiled program: A program called a compiler creates a binary executable from the source code. Programs written in C, C++ and Visual Basic (to name just a few languages) are compiled. Most commercial, proprietary software is compiled. Binaries can be distributed without source code. Interpreted program: The source code is converted to executable code by an an iterpereter program when the program is run. Depending on the language, this may be done one line at a time (pure interpreted) like DOS/Windows batch files or UNIX shell scripts, or the entire program may be converted to executable code in memory, then executed when the program is launced (Java and perl work this way). |
#2
|
|||
|
|||
![]()
There is also no reason that a hand history parser has to live on a web site. I believe there is a tool which packages up perl scripts into windows executables. If you really care about your privacy you would want to be using that type of tool.
Honestly I don't see this as being super valuable code as I am guessing that 10-20 hours for someone that understands regular expressions and HTML (or whatever output language you want) seems very reasonable. What that means is that I would expect most commmercial companies to just avoid your code if it is GPL (it isn't worth aggravation of dealing with the gpl (you have to factor you app to prevent having to release your IP)). Now having that website is some prime advertising real estate for someone targeting serious poker players.... |
#3
|
|||
|
|||
![]()
Yeah, most companies can avoid the code, but if the task is as easy as you say they are also going to enjoy precious little advantage. Which I think is nice, since poker players, serious or not, get targetted with enough crap as is.
|
#4
|
|||
|
|||
![]()
[ QUOTE ]
I believe there is a tool which packages up perl scripts into windows executables. If you really care about your privacy you would want to be using that type of tool. [/ QUOTE ] This won't protect your source code. Interpreted languages are hard to obfuscate the code for. I am not a big fan of obfuscation for a variety of reasons. Attaching an open source license to the code will protect you more than any technological trick. The tool is in the perl toolkit from activestate in case you want to know. It's kinda cool really. -D |
#5
|
|||
|
|||
![]()
[ QUOTE ]
[ QUOTE ] I believe there is a tool which packages up perl scripts into windows executables. If you really care about your privacy you would want to be using that type of tool. [/ QUOTE ] This won't protect your source code. Interpreted languages are hard to obfuscate the code for. I am not a big fan of obfuscation for a variety of reasons. Attaching an open source license to the code will protect you more than any technological trick. The tool is in the perl toolkit from activestate in case you want to know. It's kinda cool really. -D [/ QUOTE ] I was talking about protecting the user from the website not the code. As I said, the code doesn't have ton of value but it is nice to not have to reinvent the wheel. Note when I say the code isn't valuable I mean in a monetary sense not in the sense of being usefull. |
![]() |
|
|