Rubinius language/exception_spec failures
-
Key: JRUBY-1069
URL: http://jira.codehaus.org/browse/JRUBY-1069
Project: JRuby
Issue Type: Bug
Reporter: Charles Oliver Nutter
Assign
Rubinius core/time_spec failures
Key: JRUBY-1068
URL: http://jira.codehaus.org/browse/JRUBY-1068
Project: JRuby
Issue Type: Bug
Reporter: Charles Oliver Nutter
Assignee: Thomas E Enebo
Rubinius core/thread_spec failures
--
Key: JRUBY-1067
URL: http://jira.codehaus.org/browse/JRUBY-1067
Project: JRuby
Issue Type: Bug
Reporter: Charles Oliver Nutter
Assignee: Thomas E E
Rubinius core/struct_spec failures
--
Key: JRUBY-1066
URL: http://jira.codehaus.org/browse/JRUBY-1066
Project: JRuby
Issue Type: Bug
Reporter: Charles Oliver Nutter
Assignee: Thomas E E
Rubinius core/regexp_spec failures
--
Key: JRUBY-1065
URL: http://jira.codehaus.org/browse/JRUBY-1065
Project: JRuby
Issue Type: Bug
Reporter: Charles Oliver Nutter
Assignee: Thomas E E
Rubinius core/object_spec failures
--
Key: JRUBY-1064
URL: http://jira.codehaus.org/browse/JRUBY-1064
Project: JRuby
Issue Type: Bug
Reporter: Charles Oliver Nutter
Assignee: Thomas E E
Rubinius core/math_spec failures
Key: JRUBY-1063
URL: http://jira.codehaus.org/browse/JRUBY-1063
Project: JRuby
Issue Type: Bug
Reporter: Charles Oliver Nutter
Assignee: Thomas E Enebo
Rubinius code/matchdata_spec failures
-
Key: JRUBY-1062
URL: http://jira.codehaus.org/browse/JRUBY-1062
Project: JRuby
Issue Type: Bug
Reporter: Charles Oliver Nutter
Assignee: Thom
Rubinius core/kernel_spec failures
--
Key: JRUBY-1061
URL: http://jira.codehaus.org/browse/JRUBY-1061
Project: JRuby
Issue Type: Bug
Reporter: Charles Oliver Nutter
Assignee: Thomas E E
Rubinius core/float_spec failures
-
Key: JRUBY-1060
URL: http://jira.codehaus.org/browse/JRUBY-1060
Project: JRuby
Issue Type: Bug
Reporter: Charles Oliver Nutter
Assignee: Thomas E Ene
Rubinius core/fixnum_spec failures
--
Key: JRUBY-1059
URL: http://jira.codehaus.org/browse/JRUBY-1059
Project: JRuby
Issue Type: Bug
Reporter: Charles Oliver Nutter
Assignee: Thomas E E
Rubinius core/file_spec failures
Key: JRUBY-1058
URL: http://jira.codehaus.org/browse/JRUBY-1058
Project: JRuby
Issue Type: Bug
Reporter: Charles Oliver Nutter
Assignee: Thomas E Enebo
Rubinius core/exception_spec failures
-
Key: JRUBY-1057
URL: http://jira.codehaus.org/browse/JRUBY-1057
Project: JRuby
Issue Type: Bug
Reporter: Charles Oliver Nutter
Assignee: Thom
Rubinius core/enumerable_spec failures
--
Key: JRUBY-1056
URL: http://jira.codehaus.org/browse/JRUBY-1056
Project: JRuby
Issue Type: Bug
Reporter: Charles Oliver Nutter
Assignee: Th
Rubinius dir_spec failures
--
Key: JRUBY-1055
URL: http://jira.codehaus.org/browse/JRUBY-1055
Project: JRuby
Issue Type: Bug
Reporter: Charles Oliver Nutter
Assignee: Thomas E Enebo
At
Rubinius continuation_spec failures
---
Key: JRUBY-1054
URL: http://jira.codehaus.org/browse/JRUBY-1054
Project: JRuby
Issue Type: Bug
Reporter: Charles Oliver Nutter
Assignee: Thomas E
Rubinius class_spec failures
Key: JRUBY-1053
URL: http://jira.codehaus.org/browse/JRUBY-1053
Project: JRuby
Issue Type: Bug
Reporter: Charles Oliver Nutter
Assignee: Thomas E Enebo
{nofo
Rubinius binding_spec failures
--
Key: JRUBY-1052
URL: http://jira.codehaus.org/browse/JRUBY-1052
Project: JRuby
Issue Type: Bug
Reporter: Charles Oliver Nutter
Assignee: Thomas E Enebo
{
Rubinius bignum_spec failures
-
Key: JRUBY-1051
URL: http://jira.codehaus.org/browse/JRUBY-1051
Project: JRuby
Issue Type: Bug
Reporter: Charles Oliver Nutter
Assignee: Thomas E Enebo
{no
Fascinating. Creating a windows shortcut didn't really
work, but it made me realize that #!/usr/bin/env ruby
wasn't what caused ruby to be invoked. It was the .rb
file association on Windows. (God, I'm slow today.)
Changing the file associations for .rb and .rbw causes
the correct interpreter to
I guess I'm used to the &&, || v and, or thing as a long time Perl
programmer, but why not use them as they are made?
&&, || : normally.
and, or : when you specifically want the lower precedence operator.
The language specification gives them particular (and useful) meaning, I
don't think you wa
I can live with having only one version. I haven't
had much success getting windows shortcuts to work
like unix symlinks in the past, but maybe this will
be the exception...
Thomas E Enebo wrote:
If you softlink jruby to ruby and put it higher in the path than C
ruby you should be ok. Kind of r
Brilliant minds think alike. I had finally come to my
senses and realized that I wanted to eval the thing
as a string, so I coded something very similar:
puts eval('"' + template + '"')
At the moment, both idioms produce the same result:
Errors on the quotation marks embedded in the HTML.
So
Eric Armstrong wrote:
I'm reading a file into a string like this:
template = File.open("test.dwt").readlines.join
My hope was to interpolate the #{variables} in the
file with the values defined in the program. The
first attempt didn't work:
puts template
Nor did the second:
puts eval
I'm reading a file into a string like this:
template = File.open("test.dwt").readlines.join
My hope was to interpolate the #{variables} in the
file with the values defined in the program. The
first attempt didn't work:
puts template
Nor did the second:
puts eval(template)
So for me,
If there is a file named date.rb in the same dir that contains a file that
requires 'yaml' an exception is thrown when you run the file requiring 'yaml'
-
If you softlink jruby to ruby and put it higher in the path than C
ruby you should be ok. Kind of rough if you want both Rubys in your
path.
-Tom
On 5/31/07, Eric Armstrong <[EMAIL PROTECTED]> wrote:
Good thought. But I'm afraid I was far more stupid
than that. I was executing therush.rb, whic
IO.open not defined
---
Key: JRUBY-1049
URL: http://jira.codehaus.org/browse/JRUBY-1049
Project: JRuby
Issue Type: Bug
Components: Core Classes/Modules
Affects Versions: JRuby 1.0.0RC2
Environment: OS X
Calling IO.new with invalid file descriptor raises NativeException
--
Key: JRUBY-1048
URL: http://jira.codehaus.org/browse/JRUBY-1048
Project: JRuby
Issue Type: Bug
Co
IO.for_fd missing
-
Key: JRUBY-1047
URL: http://jira.codehaus.org/browse/JRUBY-1047
Project: JRuby
Issue Type: Bug
Components: Core Classes/Modules
Affects Versions: JRuby 1.0.0RC2
Environment: OS X 10.
JRuby regex support for "\G" is different than MRI
--
Key: JRUBY-1046
URL: http://jira.codehaus.org/browse/JRUBY-1046
Project: JRuby
Issue Type: Bug
Components: Core Classes/Modules
Alexey Verkhovsky wrote:
Personally, I like 'and' and 'or' because it often reads better than &&
and ||.
Especially in statement like
redirect_to :action => "show" and return
or
foo = find_foo or raise 'Foo not found'
I'm not opposed to and/or for these cases. Perhaps it's better to say
"al
On 5/31/07, Eric Armstrong <[EMAIL PROTECTED]> wrote:
Ruby Code:
- always use && and ||, not 'and' and 'or'
Why is that? For consistency with Java? Or is there
some other benefit?
This is a convention in Rails core. Its origin is that 'and' and 'or'
have priority lower than && and ||, and lo
Ola Bini wrote:
This is good news: http://www.cuddletech.com/blog/pivot/entry.php?id=822
That is one /hell/ of an endorsement.
Jason Hoffman gives the /definitive/ talk on how
to make web apps sing. He defines the complete
hardware/software stack from ethernet cables to
Solaris, and shows how a
Weighing in late. All of these make sense to me,
except for this one:
> Ruby Code:
> - always use && and ||, not 'and' and 'or'
Why is that? For consistency with Java? Or is there
some other benefit?
Charles Oliver Nutter wrote:
First a thread, then a wiki page after everyone's weighed in. Foll
When it's possible to do, I'd love to see it happen.
One less gem to install when I download. (Rake & Rspec
are automatic.)
Charles Oliver Nutter wrote:
Any reason not to? Everyone seems to be trending toward using RSpec for
testing/spec'ing these days, and it sure feels like a core sort of
fea
Good thought. But I'm afraid I was far more stupid
than that. I was executing therush.rb, which contains
#!/usr/bin/env ruby
So the C Ruby gems-library reader was being invoked. (Doh!)
I wonder. Might it be possible to redirect such scripts
so they automatically run under JRuby, instead? (I'
Consumers of ByteList.bytes field are not ByteList.begin aware
--
Key: JRUBY-1045
URL: http://jira.codehaus.org/browse/JRUBY-1045
Project: JRuby
Issue Type: Bug
Components
MenTaLguY wrote:
Eric Armstrong wrote:
...Even though my path shows
%JRUBY_HOME%\bin, executing "jruby" produces "not a
command".
Try spelling out the full path, rather than using %RUBY_HOME%.
I don't think Windows creates the registry value for the default
PATH as a REG_EXPAND_SZ by defa
JvYAMLb doesn't use ByteList.begin when accessing ByteList.bytes
Key: JRUBY-1044
URL: http://jira.codehaus.org/browse/JRUBY-1044
Project: JRuby
Issue Type: Bug
Compon
Java proxy InvocationHandler's parameterTypeCache should be thread-safe
Key: JRUBY-1043
URL: http://jira.codehaus.org/browse/JRUBY-1043
Project: JRuby
Issue Type: Bug
Array block args not expanded when calling explicit block argument
--
Key: JRUBY-1042
URL: http://jira.codehaus.org/browse/JRUBY-1042
Project: JRuby
Issue Type: Bug
Co
unicode passed in via -e is not getting encoded/decoded properly
Key: JRUBY-1041
URL: http://jira.codehaus.org/browse/JRUBY-1041
Project: JRuby
Issue Type: Bug
Compon
Ok, the current plan is for RC3 on Friday. There's outstanding bugs, but
most of them are getting into more obscure Ruby territory or into Java
integration stuff we're just not going to tackle right now. So we're
thinking an RC3 release Friday gives folks the weekend and most of next
week to gi
44 matches
Mail list logo
