Looks great, only a few notes:
* Ruby version guards inlince in the example are not allowed. You
should always use the version guard and in its block define the
example outlining the specific behaviour on that version. This means
some examples will have to broken up into smaller ones.
* To c
On Sun, Aug 2, 2009 at 2:13 PM, Laurent Sansonetti wrote:
> That's weird, did you do rake and rake install before starting the specs? I
> think it must be done otherwise the C extension bundles won't be properly
> loaded. (We should pass the appropriate flags to mspec so that it loads C
> extensio
The other day I also had the specs crashing. To fix it I had to remove
the installed MacRuby (/Library/Frameworks/MacRuby.framework/Versions/
0.5), followed by a rake clean/rake/rake install.
That's weird, did you do rake and rake install before starting the
specs? I think it must be done ot
That's weird, did you do rake and rake install before starting the
specs? I think it must be done otherwise the C extension bundles won't
be properly loaded. (We should pass the appropriate flags to mspec so
that it loads C extension bundles from the local build directory.)
If it's still cr
Hi, I'm getting the following after pulling the latest sources:
BEGIN Transcript:
darnoc-laptop:macruby-experimental conradwt$ sw_vers
ProductName: Mac OS X
ProductVersion: 10.6
BuildVersion: 10A421a
darnoc-laptop:macruby-experimental conradwt$ rake spec:ci
(in /Users/conradwt/macruby.dir/project
Welcome back \o/
$ sw_vers
ProductName:Mac OS X
ProductVersion: 10.6
BuildVersion: 10A421a
$ rake spec:ci
(in /Users/lrz/src/macruby-experimental)
./mspec/bin/mspec ci -I./lib -B ./spec/macruby.mspec :full
MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
...
Done, would you mind checking that I did it according to the rubyspec
standards?
Thanks,
- Matt
On Sun, Aug 2, 2009 at 11:30 AM, Matt Aimonetti wrote:
> Thanks for the tip, I'll go back and fix strscan and will make the
> modifications before pushing stringio.
>
> - Matt
>
>
> On Sun, Aug 2, 20
Thanks for the tip, I'll go back and fix strscan and will make the
modifications before pushing stringio.
- Matt
On Sun, Aug 2, 2009 at 11:22 AM, Eloy Duran wrote:
> Thanks Matt :)
>
> Indeed, in order to specify the API changes between 1.8 and 1.9 you should
> use version guards:
>
> ruby_ver
Thanks Matt :)
Indeed, in order to specify the API changes between 1.8 and 1.9 you
should use version guards:
ruby_version_is "" ... "1.9" do
it "works as such on all versions prior to 1.9" do
end
end
ruby_version_is "1.9" do
it "works as such on 1.9" do
end
end
To g
Hi Eloy,
Welcome back. Unfortunatelly, due to API changes, the specs can't
all pass on 1.8 and 1.9 unless we use a version check mechanism.
My understanding was that we should focus on 1.9.2 preview 1.
What do you want me to do?
- Matt
Sent from my iPhone
On Aug 2, 2009, at 6:42, Eloy Du
Hi,
I'm un-jet lagging a bit, so I thought I'd update the ruby specs
again. We are now passing: 18160 examples.
@Matt: Great work on the StringScanner! Could you please make sure the
specs run on 1.8 as well? Currently 4 fail:
$ mspec -B ruby.1.8.mspec library/stringscanner
StringScanner
11 matches
Mail list logo
