On 1 Dec 2008, at 02:45, Peter Jaros wrote:
The Autotest support in Cucumber doesn't currently associate any files
with specific scenarios. It only keeps track of failed scenarios. If
any are failing, changing any file will run those scenarios. If
everything has been passing, changing any fi
On Wed, Nov 26, 2008 at 11:51 AM, Mark Wilden <[EMAIL PROTECTED]> wrote:
> And class variables are problematic in Rails in development mode because of
> class reloading.
Yes. They are.
http://www.flickr.com/photos/peeja/3056849146/
Peter
___
rspec-us
On Thu, Nov 27, 2008 at 4:12 PM, James Byrne <[EMAIL PROTECTED]> wrote:
> James Byrne wrote:
>
>>
>> I understood that the purpose of autotest was that it ONLY ran a test
>> for the changed file. However, with this setup, if I touch any file
>> anywhere in the project then the full suite of featur
Mac OSX 10.5.5(Ruby 1.8.6 installed already)
I installed Ruby 1.9.1 preview thusly:
==
port install readline
cd ruby-1.9.1-preview1
./configure --program-suffix=-trunk --with-readline-dir=/usr/local
make
make install
On Sun, Nov 30, 2008 at 4:39 PM, Avdi Grimm <[EMAIL PROTECTED]> wrote:
> I don't think it's a practice worth promulgating.
...not to mention that most noob Ruby programmers learned to use def
self.foo (or def ClassName.foo, if they are reading the 1st edition
pickaxe online), and coming across th
On Sun, Nov 30, 2008 at 4:30 PM, Matt Wynne <[EMAIL PROTECTED]> wrote:
> I think Brian has argued eloquently that class << self leaves more readable
> and maintainable code behind.
I don't think so. Nothing that has been said here has changed my
feeling that using class << self for class methods
On 28 Nov 2008, at 16:52, David Chelimsky wrote:
On Thu, Nov 27, 2008 at 8:17 PM, Mark Wilden <[EMAIL PROTECTED]> wrote:
On Thu, Nov 27, 2008 at 5:57 PM, Brian Takita
<[EMAIL PROTECTED]>
wrote:
I'm wondering if this is a discussion about taste.
I think you're right. I've been using the '
