The win32-file-stat library provides a custom File::Stat class specifically tailored for MS Windows. Examples include the ability to retrieve file attributes (hidden, archive, etc) as well as the redefinition of certain core methods that aren't implemented at all, such as File...

The win32-ipc library provides the Win32::IPC class. This is meant to serve as an abstract base class for other IPC related libraries for MS Windows, such as win32-semaphore, win32-event, and so on.

The win32-mmap library provides an interface for memory mapped IO on MS Windows.

The win32-mutex library provides an interface for creating mutex objects on MS Windows. A mutex object is a synchronization object whose state is set to signaled when it is not owned by any thread, and non-signaled when it is owned.

The win32-pipe library provides an interface for named pipes on Windows. A named pipe is a named, one-way or duplex pipe for communication between the pipe server and one or more pipe clients.

The win32-sound library provides an interface for playing various sounds on MS Windows operating systems, including system sounds and wave files, as well as querying and configuring sound related properties.

Windows Event Log API bindings from winevt.h.

A ruby DSL for modeling business logic as Finite State Machines. The aim of this library is to make the expression of these concepts as clear as possible, utilizing the expressiveness of ruby language, and using similar terminology as found in state machine theory.

Xamarin Test Cloud lets you automatically test your app on hundreds of mobile devices

An easy to use InterProcess Communication (IPC) library

Yamatanooroti is a multi-platform real(?) terminal test framework.

A no-nonsense gem for the nonsensical Zimbra API.

Zulip client for Ruby

234ewd

Index reference to Japanese correspondence relation annotate_models

Abstract Class pattern gem for Ruby

It reverse an SQL statement to a Perl SQL::Abstract JSON format.

Always Be Testing Yo! A testing framework that runs on IronWorker http://www.iron.io

HTTP lets clients send Accept headers. We should probably use that to work out what they'll accept as a response, yea?

Simple access control on controller basis