1. Shrouding
- Posted by Jeremy Cowgar Jul 12, 2008
- 788 views
If you eliminate platform() shrouded programs will no longer be platform independant. Shrouded programs are pre-parsed il code. ifdef is a compile time function and can't be used to make decisions based on the platform with shrouded programs.
We are not removing platform. However, I am interested in you shrouding. Why would you shroud when you can now translate for free using Euphoria and OpenWatcom? Is there really a need for shrouding?
Jeremy
2. Re: Shrouding
- Posted by Jeremy Cowgar Jul 12, 2008
- 768 views
If you eliminate platform() shrouded programs will no longer be platform independant. Shrouded programs are pre-parsed il code. ifdef is a compile time function and can't be used to make decisions based on the platform with shrouded programs.
We are not removing platform. However, I am interested in you shrouding. Why would you shroud when you can now translate for free using Euphoria and OpenWatcom? Is there really a need for shrouding?
I was just interested because we had this discussion a while ago on the dev list and I was really interested in what anyone thinks about shrouding vs. translating.
Jeremy
3. Re: Shrouding
- Posted by Jim C. Brown Jul 12, 2008
- 773 views
In my opinion, shrouding is only useful if you are keeping your code closed source. (Since translated code only builds and runs on a single platform, shrouding is a better method for keeping your source code hidden.)
There is also binding, but that particular case is less important for the original poster since a bound program, like a translated program, will only run under one platform.
If you eliminate platform() shrouded programs will no longer be platform independant. Shrouded programs are pre-parsed il code. ifdef is a compile time function and can't be used to make decisions based on the platform with shrouded programs.
We are not removing platform. However, I am interested in you shrouding. Why would you shroud when you can now translate for free using Euphoria and OpenWatcom? Is there really a need for shrouding?
I was just interested because we had this discussion a while ago on the dev list and I was really interested in what anyone thinks about shrouding vs. translating.
Jeremy
4. Re: Shrouding
- Posted by Jeremy Cowgar Jul 12, 2008
- 785 views
In my opinion, shrouding is only useful if you are keeping your code closed source. (Since translated code only builds and runs on a single platform, shrouding is a better method for keeping your source code hidden.)
When you distribute your code, wouldn't you normally provide an installer as well? Thus, you are limiting yourself there too. I would think if your app is designed to be cross-platform, then you will have multiple methods of delivery already, for instance included with Eu for Windows, Linux or whatever, then an installer on top of that for that platform?
Further, the translated code is a substantial increase in performance over shrouded or bound code. Wouldn't you want that for your final production app?
Jeremy
5. Re: Shrouding
- Posted by Jim C. Brown Jul 12, 2008
- 788 views
When you distribute your code, wouldn't you normally provide an installer as well?
The majority of code in the archives is not written this way. Granted, the majority of the archive is FOSS, but shrouded code has been distributed before.
Thus, you are limiting yourself there too. I would think if your app is designed to be cross-platform, then you will have multiple methods of delivery already, for instance included with Eu for Windows, Linux or whatever, then an installer on top of that for that platform?
Probably, yes. But translating would require a separate executable to be installed each time. If you distributed and installed a source .ex then you'd only have the one file. Shrouding and the ifdef system requires different shrouded files for each platform, when this formerly wasn't the case.
Since every shrouded library or app I've seen was written for a single platform, this might not be a serious issue.
Further, the translated code is a substantial increase in performance over shrouded or bound code. Wouldn't you want that for your final production app?
Jeremy
Some may be willing to give up a little in performance for a gain in the ease of being portable.
