Re: No more platform(), conditional includes, conditional functions, condit
Matt Lewis wrote:
>
> The only downside to this is for shrouded code. Originally, the platform
> call was optimized at compile time. But it was changed so that shrouded code
> could be more cross platform. I guess this puts us back to single platform
> shrouded code.
>
> But I'm not sure that many people shroud anything anymore. I can't recall
> the last time I did that. I either bind or translate.
>
We should make a decision here because I think I can make it work in either.
Here's what I would do... if not shrouded, do exactly as it does now. However, if
shrouded, all defines would turn into a constant and when a ifdef/elsifdef was
encountered, a if/elsif would be emitted. So, in shrouded code you gain no
benefit, but your code still works.
But, I am with you Matt. Is there any reason to shroud? I do not think it's
worth the extra code. In fact, I wonder if shrouding should be done away with?
At first I was thinking, maybe John Doe would like to create ultra-cool library
ABC and sell it to Euphoria programmers, but if someone really wanted to do that
!?!? then wouldn't they be better off translating their library into a Euphoria
dll file? And if not, what do other languages do that do not provide shrouding?
Me, personally? I wouldn't worry about shrouding, but others may see value in it
still. I'll start a new thread, Do you shroud?
--
Jeremy Cowgar
http://jeremy.cowgar.com
|
Not Categorized, Please Help
|
|
