adds GD.printDebug, which outputs the .swift file name, as well as the function and line of the caller.

[EstevanBR]

This duplicates the print_debug command in Godot, which prints a message, but inserts a new line with debug info, such as the file, line, and function

Here is the example gdscript output

Hello World
   At: res://folder/node.gd:50:_ready()

• new line below the print message
• indented 3 spaces (we could add a param for this indentation width)
• includes the folder/file name, relative to the res folder (we will use #fileID for this)
• includes line number (use #line) for this
• includes function name (use #function for this)

Here is the usage:

import SwiftGodot

@Godot
class ArrayTest: Node {
	override func _ready() {
		GD.printDebug("Hello World")
	}
}

Here is the output in the godot console:

Hello World
   At: BulletHellper/ArrayTest.swift:6 in _ready()

[EstevanBR]

if we use \(#fileID):\(#line) -> SomeFolder/SomeFile.swift:102 it will print the file and line in such a way that the output can be copy pasted into Xcode's shift+cmd+O Quickly Open search to go straight to the line, but including the function name makes it more like the GDScript print_debug output.

[migueldeicaza]

I think it might be better to make it usable for Xcode consumption, what do you think?

[EstevanBR]

I have a couple reservations: Not everyone will be using SwiftGodot with Xcode, or even on a mac, we have Linux and windows users as well as users on mac who use vscode instead of Xcode. But it’s probably fair to say most users of Swfit Godot are using it with Xcode.. The function name is helpful for debugging purposes IMO. Even if you use Xcode. May want to look into what other IDEs like vscode allow for their symbol lookup, but I’m not sure how much it should inform the format. Maybe there is a format Xcode can use which has the function name, I’m only aware of file/line atm. But I think it might make sense to include the function name but just put it somewhere else in the output string. ` At: \(file):\(line) in \(function)` Would probably be fine. The file:line part is easily consumed by Xcode but we also keep the context of what function it’s being calling from.

[EstevanBR]

I updated it, lmk what you think.

[migueldeicaza]

Thank you!