Log Zig Reference Documentation
Log
Current Version: 11.6.1
Chilkat.Log
Use
Add informational messages, error messages, and tagged text values to
explain what the application is doing.
Log integers, 64-bit integers, timestamps, and date/time values when
tracing state changes or timing-sensitive workflows.
Record binary data as Base64, hex, or shortened previews so byte-level
values can be inspected safely in text logs.
Compute and log hashes of data when comparing content, verifying
transformations, or avoiding full data dumps.
Clear the log and continue building new diagnostic output during
repeated operations or test runs.
For an extended overview, see
Log Class Overview.
Build readable structured diagnostic logs with nested context and tagged values.
Chilkat.Log is a lightweight structured logging helper for
creating readable diagnostic logs from application code. It can record nested
operation contexts, informational messages, error messages, timestamps,
integers, 64-bit integers, tagged values, binary data, Base64 data, hex data,
shortened data previews, and computed hashes. It is useful when code needs a
clear step-by-step record of operations, inputs, outputs, and diagnostic
values for troubleshooting.
Nested operation context
EnterContext and LeaveContext to group log
entries under readable operation names.
Messages and errors
Numbers and timestamps
Binary diagnostics
Hash logging
Clear and reuse
Log object, enter a named context for the operation,
log the important values and decisions as the code runs, leave the context,
and inspect the resulting text if troubleshooting is needed. Use
Chilkat.Log for application-level diagnostic output; use
LastErrorText on Chilkat objects for detailed diagnostics from
Chilkat method calls.
Object Creation
// Add the package once:
// zig fetch --save https://chilkatdownload.com/11.6.1/chilkat-zig-11.6.1.tar.gz
// and in build.zig:
// const chilkat = b.dependency("chilkat", .{ .target = target, .optimize = optimize });
// exe.root_module.addImport("chilkat", chilkat.module("chilkat"));
const chilkat = @import("chilkat");
// Once per process, before any other Chilkat call:
try chilkat.unlockBundle("Anything for 30-day trial");
const log = try chilkat.Log.init();
defer log.deinit();Creates the underlying native Chilkat object. Log is a one-pointer struct passed by value; copying it copies the handle (two names for one object). Returns error.OutOfMemory if the library could not allocate the object. Use an object from one thread at a time; it may be handed from one thread to another.
Releases the native object. Call it exactly once per object (usually with defer); the handle is invalid afterwards. Objects returned by methods are owned by the caller too and are released the same way.
Wraps a handle obtained from the C API (chilkat.c.CkLog), taking ownership of it. The struct's handle field goes the other way, for anything the Zig API does not cover.
Errors and memory
Methods that can fail return an error union: a method whose only outcome is success or failure returns Error!void; a method producing a string returns (Error || Allocator.Error)![:0]u8; a method producing an object returns Error!T. chilkat.Error is error{ChilkatFailed}; the reason for a failure is in getLastErrorText, and the object remains usable. Properties never fail, and methods that answer a question (hasMember, isUnlocked, ...) return a plain bool.
String arguments are [:0]const u8 (UTF-8; string literals can be passed as is). String results are copies allocated with the allocator argument and owned by the caller, so they stay valid across later calls on the same object.
const text = log.someMethod(allocator, ...) catch |err| {
const why = try log.getLastErrorText(allocator);
defer allocator.free(why);
std.debug.print("{s}\n", .{why});
return err;
};
defer allocator.free(text);Properties
DebugLogFilePath
pub fn getDebugLogFilePath(self: Log, allocator: Allocator) Allocator.Error![:0]u8
pub fn setDebugLogFilePath(self: Log, value: [:0]const u8) void
If set to a file path, this property logs the LastErrorText of each Chilkat method or property call to the specified file. This logging helps identify the context and history of Chilkat calls leading up to any crash or hang, aiding in debugging.
Enabling the VerboseLogging property provides more detailed information. This property is mainly used for debugging rare instances where a Chilkat method call causes a hang or crash, which should generally not happen.
Possible causes of hangs include:
- A timeout property set to 0, indicating an infinite timeout.
- A hang occurring within an event callback in the application code.
- An internal bug in the Chilkat code causing the hang.
LastErrorHtml
pub fn getLastErrorHtml(self: Log, allocator: Allocator) Allocator.Error![:0]u8
Provides HTML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.
topLastErrorText
pub fn getLastErrorText(self: Log, allocator: Allocator) Allocator.Error![:0]u8
Provides plain text information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.
LastErrorXml
pub fn getLastErrorXml(self: Log, allocator: Allocator) Allocator.Error![:0]u8
Provides XML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.
topLastMethodSuccess
pub fn getLastMethodSuccess(self: Log) bool
pub fn setLastMethodSuccess(self: Log, value: bool) void
Indicates the success or failure of the most recent method call: true means success, false means failure. This property remains unchanged by property setters or getters. This method is present to address challenges in checking for null or Nothing returns in certain programming languages. Note: This property does not apply to methods that return integer values or to boolean-returning methods where the boolean does not indicate success or failure.
VerboseLogging
pub fn getVerboseLogging(self: Log) bool
pub fn setVerboseLogging(self: Log, value: bool) void
If set to true, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. The default value is false. Verbose logging should only be used for debugging. The potentially large quantity of logged information may adversely affect peformance.
Version
pub fn getVersion(self: Log, allocator: Allocator) Allocator.Error![:0]u8
Methods
Clear
Clears all existing log entries and starts a new log whose top-level context is named initialTag.
Log* methods. The completed structured log can be inspected through the Log object's diagnostic text, such as LastErrorText.EnterContext
Begins a nested logging context named tag. Entries written after this call are grouped inside the new context until a matching LeaveContext is called.
EnterContext with LeaveContext. Contexts may be nested to reflect operation hierarchy.LeaveContext
Ends the current nested logging context and returns logging to its parent context.
LogData
Adds a tagged text value to the current context. The output associates tag with message, making this useful for named values such as filenames, paths, IDs, states, or protocol fields.
LogDataBase64_2
Encodes szByteData bytes beginning at pByteData as Base64 and logs the result under tag.
LogDataHex2
Encodes szByteData bytes beginning at pByteData as hexadecimal text and logs the result under tag.
szByteData readable bytes.LogDataMax
Adds a tagged text value to the current context, but limits the logged value to at most the first maxNumChars characters of message.
LogDateTime
Logs the current date and time under tag using an RFC 822-style date/time representation. If gmt is true, the logged time is GMT/UTC; otherwise local system time is used.
LogDateTime for a calendar date with timezone context. Use LogTimestamp for a time-of-day marker.LogError
Adds message as an error entry in the current logging context.
LastErrorText produced by other Chilkat objects when their operations fail.LogHash2
Computes a hash of szByteData bytes beginning at pByteData and logs the digest as hexadecimal text under tag. Supported values for hashAlg are SHA1, SHA256, SHA384, SHA512, and MD5.
MD5 and SHA1 are not suitable when cryptographic collision resistance is required. Prefer SHA-256 or stronger for security-sensitive hashing.LogInfo
Adds message as an informational entry in the current logging context.
LogData when the entry is better represented as a named value.LogInt
Adds the integer value to the current log under tag.
LogInt64
Adds the signed 64-bit integer value to the current log under tag.
LogTimestamp
Logs the current time-of-day under tag in HH:MM:SS:mmm form, where mmm represents milliseconds.