Displaying 7 results from an estimated 7 matches for "backward_compat".
Did you mean:
backwards_compat
2010 Jun 10
1
RSpec 2: uninitialized constant - mocking belongs_to AR relation
gems/ruby-1.9.2-head/bundler/gems/rspec-
core-2398fcadf5beb256bed9c548c59445d3b4c8a047-master/lib/rspec/core/
backward_compatibility.rb:26:in `const_missing'': uninitialized
constant Message::User (NameError)
from /Users/kristianconsult/.rvm/gems/ruby-1.9.2-head/bundler/gems/
rspec-expectations-996c752171a0a0e16347e934dadc25767e31186c-master/lib/
rspec/expectations/backward_compatibility.rb:6:in `const_missing...
2010 Oct 06
2
rspec2 observations
...*****************************
DEPRECATION WARNING: you are using a deprecated constant that will
be removed from a future version of RSpec.
* Spec is deprecated.
* RSpec is the new top-level module in RSpec-2
/Users/cremes/.rvm/gems/rbx-head/gems/rspec-expectations-2.0.0.rc/lib/rspec/expectations/backward_compatibility.rb:6:in `const_missing''
*****************************************************************
I don''t know if this is an issue with RSpec-2 or if Rubinius & JRuby require an update. Or, perhaps the problem is elsewhere and this warning is a red herring. Guidance on this w...
2010 Aug 30
1
in a rails3 - rspec then require 'authlogic/test_case' and now I broke stuff?
...Users/rick/.rvm/rubies/ruby-1.9.2-preview3/bin/ruby -S bundle exec
/Users/rick/.rvm/rubies/ruby-1.9.2-preview3/bin/ruby -Ilib -Ispec
"./spec/models/meter_spec.rb" "./spec/models/user_spec.rb"
/Users/rick/.rvm/gems/ruby-1.9.2-preview3/gems/rspec-core-2.0.0.beta.20/lib/rspec/core/backward_compatibility.rb:20:in
`const_missing'': uninitialized constant ActionMailer::TestCase::Behavior
(NameError)
from
/Users/rick/.rvm/gems/ruby-1.9.2-preview3/gems/rspec-expectations-2.0.0.beta.20/lib/rspec/expectations/backward_compatibility.rb:6:in
`const_missing''
from
/Users/rick/...
2010 Apr 11
0
[LLVMdev] Proposal: stack/context switching within a thread
Having read through Stackless Python's web pages a bit:
1. They're doing pretty much what I'd like to do, except that I don't
want to be tied to a particular language and I'd like to be able to
use the stack. (Also, stack use is inescapable with LLVM, as far as I
can tell).
2. We should be able to support "hard switching" in Stackless Python
by adding a
2010 Apr 10
2
[LLVMdev] Proposal: stack/context switching within a thread
On the other hand, stack manipulation really ought to be handled by
the target, since only the target knows the details of how the stack
is laid out to begin with. Also, if we have stack manipulation calls
in the IR, optimization quickly becomes very difficult. Unless we
just allow optimizers to ignore the stack manipulations and assume
they're doing the "right" thing.
On the
2010 Apr 11
3
[LLVMdev] Proposal: stack/context switching within a thread
...that
> forces recursive calls to spawn a new context and turns large alloca's
> into malloc's, making it safer to have a bunch of little stacks
> without any needed juggling.
This sounds like a stopgap until real split stacks can be implemented.
http://gcc.gnu.org/wiki/SplitStacks#Backward_compatibility describes
some of the other difficulties in getting even this much to work.
(foreign calls, and function pointers, at least)
2010 Apr 11
0
[LLVMdev] Proposal: stack/context switching within a thread
...sive calls to spawn a new context and turns large alloca's
>> into malloc's, making it safer to have a bunch of little stacks
>> without any needed juggling.
>
> This sounds like a stopgap until real split stacks can be implemented.
> http://gcc.gnu.org/wiki/SplitStacks#Backward_compatibility describes
> some of the other difficulties in getting even this much to work.
> (foreign calls, and function pointers, at least)
>
True. Some front-ends have more control over this than others,
though. And users of a C-like
front end would find this pass helpful even though they&...