On Mar 30, 2008, at 6:29 AM, Ken Shmidheiser wrote:
> FBtoC already gives us:
>
> 1. Straight path to FSRefs since FSSpecs are broken with long file  
> names.
> 2. A new syntax that allows us to add directly to a bundle  
> resources of theorectically unlimited size and available to all the  
> current CFBundle Toolbox, thus  bypassing Classic Resources-- and  
> their cumbersome limitations: limitations on size, destruction of  
> application when moving cross platform, locking and unlocking  
> memory when they're moved, opening and disposing them without  
> crashing, adding and subtracting them without crashing or  
> disrupting the order of, say, the stringlists, etc.
>
>   OH NO! It's going to break all my old code that uses resources  
> and I have thousands of them!
>
>
> 3. Ability to compile directly with either a C or ObjectiveC  
> compiler into fully Carbon-compatible code.
>
>
> 4. Ability to generate fast, stable Universal Binaries.
> 5. Ability to localize in foreign languages.
> And Robert Purves has already outlined benefits of doing 'for'  
> loops like everyone else in the world:
>
> [1] No more tiresome workarounds.
>
> [2] Standard C 'for' loops are easier (for humans) to read than  
> 'do  {...} while' in the translated code.
>
>   [QUESTION: How many of you have attemped to translate Apple's  
> sample source code and had to replace each 'for' loop with an FB  
> 'do/while' loops to get things to work? Speaking from long  
> experience, it's not fun.]
>
> [3] OpenMP is coming to OS X soon (available in beta now). It is  
> an  extension to C that allows parallel threaded computation, as  
> on  supercomputers. OpenMP requires standard C 'for' loops, which  
> it can  speed up by a factor equal to the number of processor  
> cores. Every FB  programmer will want his FBtoC-built apps to be  
> OpenMP-savvy, making  use of the previously comatose 7 cores of a  
> Mac Pro.

Thanks Ken. Enjoyed it very much.


Brian S.