Quote from Forum Archives on March 28, 2022, 8:01 am

Posted by: richlove <richlove@...>

Max,

 

#if def _NSLog

That is a good way to control your NSLogs.

 

I also did not know about the NSLog menu item until recently.

It is a good way to toggle NSLogs on and off (Does not require any extra code).

 

The problem I am having is when you make an Xcode project.

If you use #if def _NSLog, all of the NSLogs are ignored and not used when you make an Xcode project.

 

And if you use the NSLog menu to toggle it on, the results are unreliable at best when you make an Xcode project.

You can get it to use the NSLog statements in Xcode by first deleting the .m file in your Xcode project.

But the format of the NSLog statement is wrong.

Instead of NSLog( @"Welcome to NSLog")

What you get is  nsLog( CFSTR( "Welcome to NSLog" ) ); 

That fails when you build in Xcode.

To make it work, you need to change it to NSLog( @"Welcome to NSLog");

And you also need to comment this out in the .h file       #import <NSLog/NSLog.h>

 

So to make a long story short,

When the NSLog menu it enabled, it would be perfect if FutureBasic would just transfer the NSLog statements to Xcode unchanged and just add a semicolon.

NSLog( @"Welcome to NSLog");

And also should not add the #import <NSLog/NSLog.h>  to the .h file.

 

Rich

 

 

 

 

 

Carnation Software

 

MacWise Terminal emulation for Macintosh

http://www.CarnationSoftware.com

[email protected]

512 858-9234

 

 

From: <[email protected]&gt; on behalf of MAX TAYLOR <[email protected]&gt;
Reply-To: <[email protected]&gt;
Date: Sunday, March 27, 2022 at 9:52 PM
To: F B <[email protected]&gt;
Subject: [FB] NSLog Behavior

 

I have always been one to be in control of my code but today I discovered, by accident the FB “Debug” showing “NSLog” so out of curiosity I selected it, much to my dismay.

 

For countless years since NSLog because available to us FB users I have used code something like this below. Many years ago I had asked Bernie if he would put a flag in NSLog so we could test, at any time or place in our code whether or not NSLog had been included in our application. He thought it would do no harm and he added “_NSLog” so we could test for it.

 

Below is just one example of how I have used the NSLog flag that Bernie installed.

 

#if def _NSLog

 

FontRef font = fn FontWithName( @"Helvetica", 12.0 )

NSLogSetFont( font )

 

NSLogSetTitle( @"NSLog Window" )

 

NSLog( @"FB Runtime version: %@&quot;, CustomFBVersionStr )

NSLog( @"FB Project version: %@, %@&quot;, CustomVersionStr, CustomBuildStr )

NSLog( @"FB Project name   : %@&quot;, CustomProjectNameStr )

NSLog( @"FB Project author : %@&quot;, CustomAuthorStr )

NSLog( @"Welcome to NSLog  : v%@&quot;, NSLogVers)

NSLog( @"-----------------------------------------")

#endif

 

Through my code I have these NSLog “#if def _NSLog/#endif statements that allow me to selectively turn On/Off log statement but simply including or commenting out the NSLog include statement.

 

I also use the following special flags in certain places.

 

#if def _NSLog

_ShowLogs     = 1

_ShowCodeLogs = 1

#endif

 

This allows me to have complete control of NSLog statements that also may appear in my code files.

 

 

—————————

by: Max Emmons Taylor Jr. ©

FB 7.0.12

OS 12.2.1 Monterey

Xcode 13.3

4VFK20629

—————————

 

--
To unsubscribe, send ANY message to: [email protected] To access the list archives, go to: http://freegroups.net/groups/futurebasic/

--
To unsubscribe, send ANY message to: [email protected] To access the list archives, go to: http://freegroups.net/groups/futurebasic/