On 19 May 2012, at 06:13, Brian S <fblistserve@...> wrote:

> 
> On May 18, 2012, at 7:06 PM, Ken Shmidheiser wrote:
> 
>> Can we grandfather Bernie's FBLog.incl (with his permission, of course) into the headers of the next FB release?
> 
> 
> Where to put it and which one to use are the questions ( since there is no question of the includes value ).
> 
> Which one to use:
> 
> Bernie’s input would be helpful but there appear to be at least two versions of this include in use:
> 
> (1) FB_5_7_2_Examples/Miscellaneous/FBLog/ has been there since early 2011 or so. It relies on a carbon nib and uses C code and HIViewxxxxx. The FBLog command nicely accepts multiple and unlimited arguments just like printf, NSLog etc. 
> 
> (2) Bernie’s FBNS suite has an FBNSLog. Advantages: all Objective-C, no nib required. FBNSLog also accepts multiple and unlimited arguments like FBLog.
> 
> (3) I’ve also seen demos including "NSLog.incl" but I’m assuming that is just a renamed version of FBNSlog
> 
> IMO #2 is superior to #1 and it was probably Bernie’s intent to upgrade the FBLog code.
> 
> Where to put it:
> 
> We could replace FBLog in the directory referenced in #1 with Bernie’s FBNS Log. 
> 
> Advantages: The FB5 deliverable doesn’t grow any larger and the code is still available to those who need it. The current beta of FB 5.7.3 weighs in at approximately 8.1 MB. 
> 
> Disadvantage: Requires an extra step. If in the headers only an Include or Project entry needed.
> 
> Another observation: FBNSLog would typically be used for debugging and wouldn’t typically be left in a compiled deliverable for the customer or the Mac App Store. A perusal of our Headers doesn’t reveal any debugging headers. All that code assists with implementation features.
> 
> Brian S.
> 

I suspect FBNSLog is the better version, but maybe renamed to FBLog. Will take a look after the weekend, unless someone here beats me to it.

Suggestions welcome (KS, SVV,...?)

Bernie [iPhone]