From: Eric Wong <normalperson@yhbt.net>
To: ruby.io.splice@librelist.com
Subject: dropping 1.8 compatibility?
Date: Thu, 27 May 2010 00:29:25 -0700 [thread overview]
Message-ID: <20100527072925.GA16976@dcvr.yhbt.net> (raw)
In-Reply-To: <20100527072925.GA16976@dcvr.yhbt.net>
Hi all,
I've noticed that 1.8 support is actually broken in corner cases if
blocking file descriptors are exposed to this library.
Since it's time consuming to maintain 100% proper 1.8 compatibility with
the green threading implementation, I'm strongly considering just
dropping it.
Actually, is anybody using this at all besides me? :)
--
Eric Wong
next parent reply other threads:[~2010-05-27 7:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 7:29 Eric Wong [this message]
2010-05-27 20:47 ` dropping 1.8 compatibility? Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://yhbt.net/ruby_io_splice/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100527072925.GA16976@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=ruby.io.splice@librelist.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/ruby_io_splice.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).