On Nov 28, 7:07 pm, Mislav Marohnić [EMAIL PROTECTED]
wrote:
On Nov 28, 2007 4:54 PM, Viktor Kojouharov [EMAIL PROTECTED] wrote:
If a function can take an argument, and you'd expect to get a boolean in
some cases, but an object in others, what would you do?
In my opinion, a function
On Nov 28, 2007 4:54 PM, Viktor Kojouharov [EMAIL PROTECTED] wrote:
If a function can take an argument, and you'd expect to get a boolean in
some cases, but an object in others, what would you do?
In my opinion, a function that returns booleans in some cases and objects in
others is a poor
On Nov 28, 2007 6:07 PM, Mislav Marohnić [EMAIL PROTECTED] wrote:
In my opinion, a function that returns booleans in some cases and objects
in others is a poor designed function.
Oops, I meant to say poorly* designed function.
--~--~-~--~~~---~--~~
You
I must've missed this one. The second patch still stands though.
On Nov 26, 1:00 am, Sam Stephenson [EMAIL PROTECTED] wrote:
On Nov 24, 2007, at 11:32 AM, Viktor Kojouharov wrote:
I've submitted a patch to trac for your consideration, which adds
array slices a' la Ruby
On Nov 24, 2007, at 11:32 AM, Viktor Kojouharov wrote:
I've submitted a patch to trac for your consideration, which adds
array slices a' la Ruby
http://dev.rubyonrails.org/ticket/10268
Array objects in JavaScript already have a method called slice:
