The Rubinius Language Platform
MPL-2.0 License
Bot releases are hidden (Show)
Published by brixen over 9 years ago
Version 2.5.7 (2015-06-16)
News:
Changelog:
Published by brixen over 9 years ago
Version 1.4.8 (2015-06-09)
News:
Changelog:
Published by brixen over 9 years ago
Version 2.5.6 (2015-06-12)
News:
Changelog:
Published by brixen over 9 years ago
Version 1.4.7 (2015-05-20)
News:
Changelog:
Published by brixen over 9 years ago
Version 2.5.5 (2015-05-15)
News:
Changelog:
RbConfig::CONFIG['THREAD_MODEL']
(Yorick Peterse)Published by brixen over 9 years ago
Version 2.5.4 (2015-05-13)
News:
Changelog:
Published by brixen over 9 years ago
Version 2.5.3 (2015-04-28)
News:
Changelog:
Published by brixen over 9 years ago
Version 1.4.6 (2015-04-28)
News:
Changelog:
Published by brixen over 9 years ago
Version 1.4.5 (2015-04-27)
News:
Changelog:
Published by sshao over 9 years ago
Version 1.4.4 (2015-03-19)
News:
Changelog:
Published by brixen over 9 years ago
Version 1.4.3
News:
Changelog:
Published by brixen over 9 years ago
Version 1.4.2 (2015-01-30)
News:
Changelog:
Published by brixen over 9 years ago
Version: 2.5.2 (2015-01-30)
News:
Changelog:
Published by brixen over 9 years ago
Version 1.4.1 (2015-01-26)
News:
The developer tools and IRB are included in the release builds again.
All changes from master for 2.5.1 that are not language version dependent are
merged into 1.8.7 branch.
Changelog:
Published by brixen over 9 years ago
Version: 2.5.1 (2015-01-26)
News:
Changelog:
Published by brixen almost 10 years ago
Version: 2.5.0 (2015-01-17)
News:
Process.spawn has been improved by not relying on the virtual machine to be
in a partially functioning state after fork() is called and before exec() is
called. All the subprocess state setup is done in the VM itself now, rather
than calling back to Ruby. This significantly improves reliability.
The JIT has been improved to be more transparent. Previously, JIT failures
could impact the semantics of running Ruby code. This is contrary to the
purpose of a JIT, which is to provide exactly the same Ruby semantics while
optimizing the execution of the Ruby code.
The JIT metrics are now emitted correctly. See the following blog post about
using the Rubinius Metrics with InfluxDB and Grafana:
http://rubini.us/2015/01/05/rubinius-metrics-meets-influxdb-part2/
The Psych gem is now pre-installed to provide YAML functionality. This
replaces the previous use of Syck to bootstrap YAML for RubyGems.
RubyGems is updated to 2.4.5.
Bundler is updated to 1.7.12.
Changelog:
Published by brixen almost 10 years ago
Version: 2.4.1 (2014-12-04)
News:
Several C-API now resolve autoloads when looking up a constant:
o rb_path2class
o rb_path_to_class
o rb_const_get
o rb_const_get_at
o rb_const_get_from
The MRI C-API defines a number of constants that are specific to MRI's
garbage collector and should never be used outside of MRI itself.
Unfortunately, gems like Psych do use them, so we are forced to define them.
o RUBY_DEFAULT_FREE
o RUBY_NEVER_FREE
o RUBY_TYPED_DEFAULT_FREE
o RUBY_TYPEED_NEVER_FREE
o RUBY_TYPED_FREE_IMMEDIATELY
o RUBY_TYPED_WB_PROTECTED
The C-API defines the Check_TypedStruct constant.
Kernel#require_relative uses the current working directory when called in
contexts like IRB or -e where a file does not define the relative path.
File.fnmatch support for FNM_EXTGLOB and FNM_PATHNAME is improved.
Changelog:
Published by brixen almost 10 years ago
Version: 2.4.0 (2014-12-01)
This release is dedicated to the memory of Ezra Zygmuntowicz, a very good
friend to Rubinius, Ruby, and Rails. Thank you, Ez.
News:
Changelog:
Published by brixen almost 10 years ago
Version: 2.3.0 (2014-10-31)
News:
Keyword arguments (both optional and required) are supported. Other syntax
changes in MRI 2.1, like Complex and Rational literal suffixes and symbol
list literals, are also supported.
Rubinius will read -X configuration options from CWD/.rbxrc. The format of
the file is one -X configuration option per line. The available -X
configuration options are listed by the -Xhelp option.
The basic infrastructure has been added for always-on metrics of Rubinius
subsystems. The metrics are 64bit monotonic counters. The data is accessible
with 'Rubinius::Metrics.data'. The object returned provides the following
methods:
The metrics can be emitted to StatsD at a regular interval. See the
following -X configuration options:
The available metrics will be refined over time. Check the values returned
by the 'Rubinius::Metrics.data.keys' method to determine which metrics are
available.
Rubinius provides an interface to the syslog facility. This is used
internally in Rubinius subsystems to standardize logging. Since the syslog
interface available through libc only allows syslog to be opened once in a
process, Rubinius provides the Rubinius::Logger class as a way for
applications to use the same handle to syslog but provide a specific prefix
for the application (or application components).
The default level that will be written to the log is Warn or higher. To
change the log level, use the system.log.level -X configuration option.
The system.log -X configuration variable controls which logger is used. The
available loggers are syslog, console, or path. The default logger is the
file /var/log/$PROGRAM_NAME.log, where $PROGRAM_NAME is replaced by the
value of Rubinius::PROGRAM_NAME. If this file is not writable,
$TMPDIR/$PROGRAM_NAME.log (where TMPDIR is an environment variable) or
/tmp/$PROGRAM_NAME.log will be used, if writable.
If using another application component that opens syslog, this will
interfere with Rubinius using syslog. In this scenario, consider using the
Rubinius::Logger class in your application.
The infrastructure for Rubinius::Console has been added. Rubinius::Console
will eventually replace IRB, the Rubinius debugger and profiler, and all the
Rubinius::Agent features, including heap dump. Many of the Rubinius::Console
features have not yet been implemented.
The Rubinius::Console supports attaching to any running Rubinius instance as
long as read/write access is available to the file system path specified by
the system.fsapi.path -X configuration option. Accordingly, Console relies
on the OS process and file system permissions to provide security and access
control. With a utility like sshfs, Console can connect to a running
Rubinius instance over the network.
The goal of Console is to provide a single, comprehensive, integrated, and
powerful interface to the behavior of the Rubinius system and applications
running on it.
Support for automatically building LLVM from source, or accessing a
pre-built binary of LLVM has been removed. Effort is being focused on
supporting LLVM packages provided by the system. This is a better use of
time and allows Rubinius to better integrate with existing systems. For
example, many Linux distributions strenuously discourage alternately
packaging system libraries to reduce security risks when defects in the
libraries are detected and fixed.
Changelog:
Published by brixen over 10 years ago
Version: 2.2.10 (2014-06-27)