Re: ver 2.5 shroud program
Robert Craig wrote:
> I may get around to doing shrouding of include files again,
> but I would do it in a much better way next time. However
> I really don't like investing a lot in encryption, knowing that
> tomorrow, or next year, or maybe in ten years, some cracker is
> going to publish the algorithm, and then I'll encur the wrath
> of Bernie Ryan when he finds that all of his precious proprietary
> source code has been exposed for all to see. 
I personally dont like the concept behind shrouded includes all that much. The
idea that part of the program/library is readable source code, while some or all
the included files could be encryted IL makes me suspicious on what the author is
trying to conceal... perhaps a worm, or virus. Ofcourse the fine people around
here wouldn't have such intention? , that perhaps explains part of the reason
why shrouded includes were very rarely used?
However, I think it would be a very worthwhile time investment to implement TRUE
thread-safety into the translator & interpreter products for v3.0, while we good
people could do the extensive bug testing (testing thread APIs too), and later
develop a cross-platform thread library or just use a 3rd party one. This should
be done because it would make me and alot of other people very pleased, and would
help further make Euphoria a true proffessional development tool :D
Regards,
Vincent
--
Without walls and fences, there is no need for Windows and Gates.
|
Not Categorized, Please Help
|
|
