On Tuesday 17 February 2009 10:47:01 pm Charles Oliver Nutter wrote:
> ...
> As Koichiro replied, he's working on an FFI-based readline that will
> probably work better than Jline. The fork on Github will remain for
> people that want or need to build their own with any additional patches,
> and ho
Need FFI platform files generated for x86_64 windows
Key: JRUBY-3415
URL: http://jira.codehaus.org/browse/JRUBY-3415
Project: JRuby
Issue Type: Task
Reporter: Koichiro Ohba
Nick Sieger wrote:
Maybe you should rename it to jruby-jline or something to indicate how
you intend to fix things to work with JRuby. You're not necessarily
taking over maintenance of jline for any possible consumers, right?
You just want to make it work better for JRuby and will incorporate
the
Charles Oliver Nutter wrote:
I've forked Jline:
http://github.com/headius/jline/tree/master
After thinking about this a bit more, I guess I actually meant fork in
the "I want a place to commit patches" sense.
If we continue with Jline (and that's a big if) we would need to have a
full rele
Hi,
I'm developing readline-ffi now.
Because I think jline has some problems about compatibility.
For example,
* it does not support input of multibyte characters
* configuration for GNU readline such as .inputrc is not supported
The project's goal is being included in JRuby, but it is just a
Good enough for me! 1.2 is shaping up to be another great release.
Joe
On Tue, Feb 17, 2009 at 9:46 PM, Charles Oliver Nutter <
charles.nut...@sun.com> wrote:
> I appreciate your position, and I totally agree. Just look at the number of
> deprecated methods we have collected. I did a pass during
I appreciate your position, and I totally agree. Just look at the number
of deprecated methods we have collected. I did a pass during 1.2 to
strip that number down a bit (especially since many were over a year
old) but we're definitely erring on the side of caution when it comes to
user-visible
No, I don't think personally I have any code that would be effected, I'm
just thinking it might be good to formalize a process for when these kinds
of issues come up. Since the behavior was never exactly specified I don't
think this problem can be considered a "bug" that is being fixed. It's more
Is this going to affect code of yours? I suppose it could be reduced to
a warning, but it's pretty hard to fix the issue I resolved without
breaking this behavior. And for what it's worth it was never really
advocated or recommended, though I know that's little consolation.
Joseph Athman wrote
One more thing... I remember talk about a readline-ffi library. I
think development is still waiting on a windows-only ffi bug.
Are there plans to switch to that in the future? Would this fork mean
that JRuby is sticking with JLine?
Just curious
Joe
On Tue, Feb 17, 2009 at 2:45 AM, Charles Oli
Maybe you should rename it to jruby-jline or something to indicate how
you intend to fix things to work with JRuby. You're not necessarily
taking over maintenance of jline for any possible consumers, right?
You just want to make it work better for JRuby and will incorporate
the code into JRuby rele
Is there any way to deprecate the current frowned upon usage of require and
release a new point release of JRuby before 1.2? It seems a little harsh to
simply remove something that used to work (even poorly) without giving
people a nice way of checking their code for this problem. Rails seems to
New ruby_test failures
--
Key: JRUBY-3414
URL: http://jira.codehaus.org/browse/JRUBY-3414
Project: JRuby
Issue Type: Bug
Components: Core Classes/Modules
Reporter: Charles Oliver Nutter
Ideally the
On Tue, Feb 17, 2009 at 12:31 AM, Charles Oliver Nutter
wrote:
> Stephen Bannasch wrote:
>>
>> At 8:38 PM -0600 2/16/09, Charles Oliver Nutter wrote:
>>>
>>> I'm working on http://jira.codehaus.org/browse/JRUBY-3214 and I think we
>>> need to ratchet down what load and require do when loading .cla
I think this has come around a few times with Monkeybars apps for some
of our users. The workaround for it is pretty easy, but I think some
greater separation between Java and Ruby is better here. It could also
help the developer in thinking that $LOAD_PATH != $CLASSPATH, which is
a somewhat relat
Bah, didn't read the whole email... it's too early... as soon as i
clicked "send" :(
I'd say give it a new name, I doubt they'll hand it over. You might
have more clout, but they wouldn't give me commit access when I asked.
I'm pretty sure they want to remain in control of JLine.
Sorry about th
When forking a project, shouldn't you change the name of it? Linux
distributions seem likely to be annoyed if you fork and keep the same
name.
Joe
On Tue, Feb 17, 2009 at 2:45 AM, Charles Oliver Nutter
wrote:
> I've forked Jline:
>
> http://github.com/headius/jline/tree/master
>
> I know the ma
Sounds like a worthwhile change to me.
On Mon, Feb 16, 2009 at 9:38 PM, Charles Oliver Nutter <
charles.nut...@sun.com> wrote:
> I'm working on http://jira.codehaus.org/browse/JRUBY-3214 and I think we
> need to ratchet down what load and require do when loading .class files.
> They've started to
18 matches
Mail list logo