Max Taylor wrote: > If FBtoC generates these errors do you guys have a text file with > what these errors actually mean. > It seems that they are a cryptic as those that Apple generates. If > we had such a list then maybe we could figure these out on our own > without wasting your valuable time. > > Wording like: > StringExpressionContinuation: bad firstTermGenericType > What does this actually mean? > > Error:•• fn type mismatch in line 166 of SPSTSerialRoutines.incl: > IntToStr > 166: theXStr = FN IntToStr( xLong ) > ^ > Error:•• FBtoC internal error in line 166 of > SPSTSerialRoutines.incl: StringExpressionContinuation: bad > firstTermGenericType > 166: theXStr = FN IntToStr( xLong ) I think the first error message is adequate. As Brian explained, a function returning a string must have the string type-identifer suffix: IntToStr$. This annoying legacy from FB4 will be removed in the next release of FBtoC. The second message is consequential to the preceding real error and ideally would not be displayed to the goggle-eyed user. The message's meaning, if any, is known only to those with the FBtoC source code in front of them. Parsers in general tend to get confused by errors in source. When FBtoC's parser gets confused, it sometimes emits a stream of bizarre errors until it manages to resync with good code, typically at the next statement. I suggest turning on the Preferences checkbox 'Stop on first error', at top left of the FBtoC Settings window. Robert P.