On Oct 28, 2007, at 9:52 PM, Robert Purves wrote: > > maxclass@... asked: > >> Is it possible to add an addition into FBtoC to allow us to make >> minor changes to the C code in the "build_temp" folder using XCode >> and then have FBtoC run directly from the modified "build_temp" >> folder without going through the original FB code which will only >> re-generate the same errors. > > > There's no official way, but this workaround isn't especially > challenging. Max, Robert's method works but I would advise not using this approach. 1) FBtoC was not designed to allow the programmer to work directly with the C code. It is an intermediate step on the path toward an executable in the compile process. The C code is there because it needs to be generated and it is also useful for running with the Xcode debugger. 2) Generating C code for unsupported (by FBtoC) functions can be handled by the _PASSTHROUGH constant to pass C code directly. It is rarely necessary to use passthrough and many, if not most, of the situations that formally required it have been fixed. 3) Making changes directly to the C code (build_temp folder) virtually forces all subsequent maintenance and development in C, unless you are comfortable coming back and making the C changes every time. If the programmer cannot write it in FB, than FBtoC needs to be fixed. Clearly, FBtoC does not support all FB syntax, but the FBtoC team can often suggest alternative FB code (i.e. TB calls instead of FB key words that might yet be unsupported). The ONLY time I would recommend adopting Robert's method (and eliminate FBtoC) is when the programmer anticipates abandoning FB and going to C. HTH.... Brian S.