Search Results for "api code generator"

swift-log is the official, vendor-neutral logging API for Swift, providing a small, performant core that libraries and applications adopt to avoid logger lock-in. It defines common logging semantics and levels, plus a lightweight façade that backends can implement—so the same application code can run with different logging engines (e.g., OSLog on Apple platforms or custom sinks on servers).

Flogger is a structured logging API for Java that decouples how you log from where logs ultimately go, making it easy to change backends without rewriting application code. Instead of building messages eagerly, it uses lazy parameter evaluation so expensive string building only happens when a log statement is actually emitted. The API encourages structured key–value context and fine-grained rate limiting, which helps keep logs informative without flooding systems during high-traffic or error storms. ...

spdlog is a header only library. Just copy the files under include to your build tree and use a C++11 compiler. It provides a python like formatting API using the bundled fmt lib. spdlog takes the "include what you need" approach, your code should include the features that actually needed. For example, if you only need rotating logger, you need to include "spdlog/sinks/rotating_file_sink.h". spdlog provides various log targets, which are, rotating log files, daily log files, console logging (colors supported), syslog, Windows event log, and Windows debugger (OutputDebugString(..)). ...

This package allows you to manage and keep track of each one of your log files.

Log4db2 is a logging utility for DB2 LUW that uses SQL instructions with SQL PL code. Its purpose is to provide an easy way to write messages from a SQL routine, with the possibility to query these messages directly from the database, allowing to monitor the progression of a process. This utility aims to reduce the time used for developing, testing, debugging and monitoring SQL routines, by centralizing the messages produced by the code. The idea and architecture of this utility...

File system/directory monitoring utilities with loggin and task processing support (can execute files or make a WCF service call). Multiple configuration options. Source code libraries can be used to create a custom file system monitor.

...In addition to the monitoring service, there is an administration app, shown in the screenshots, which allows you to easily add new monitors. For more complete information, check out the project homepage. The complete JavaDoc is available at the homepage. The source code is freely available and can be extended to include additional metrics.

imntr (inode monitor) can be used to montior activity on files or directories. Monitoring is accomplished through the inotify API, which is available on Linux 2.6.13 and up. v1.1 added logging capabilities and cleaned up some of v1.0's code v1.2 no longer forces you to run imntr as root. If you want to monitor a privileged file, imntr will fail and tell you that you need to run imntr as root.

An open source data version repository model based on true INSERT only logic. Contains high performance support for data versioning and history. Enables point-in-time query and CDC sourcing including mapping each change to a transaction.

An implementation of the Model-View-Controller (MVC) design pattern based on the Jakarta Struts Framework. Includes a core library (Horizon), a servlet container (Stratus), and a Server Pages Engine (Phase). Resembles the J2EE web container environment.

Mezzanit.Log (Mezzlog) is a logging library which allows to make consistent, cross-assembly reports from the application runs. Final report destination (XML file, database table) can be set/changed during run-time without code re-compilation.

jLo is logging framework for java. It takes a different approach than any other logging framework available for java. It uses a code generator during the build process in order to be more flexible. You can define your own targets like init,debug, fata

Cricket Cage automatically creates JUnit TestCases for repeatable bugs and test scenarios. Include Cricket Cage's AspectJ code to install a code generator, then run the program to generate the TestCase. Finally, add the test case to your build.xml.

The goal of the A.I.G. project is to create a "front end" script that will custom build chart generation code for any environment based on user input.