Re: Shrouding

new topic     » goto parent     » topic index » view thread      » older message » newer message
Jeremy Cowgar said...

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.

Jeremy Cowgar said...

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.

Jeremy Cowgar said...

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.

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu