Hi Brian, Luis, Sorry for the confusion - it actually doesn't depend on 1.8.6, I just didn't test it on others. Seems to work down to 1.8.4 and it is almost working for 1.9. It also would conceivably work for lower versions (one just needs to test it out).
Luis, I don't know anything about Visual C, but if Mongrel is compiling with it certainly this should. Look at the extconf.rb, there is nothing to it. I've updated a few things in the extension: lowered the required ruby version and added support for splat arguments. I won't be posting here anymore about this extension (it's getting its own RubyForge project) but please check out the revision: http://s3.amazonaws.com/four.livejournal/20070905/method_args-0.0.2.gem http://s3.amazonaws.com/four.livejournal/20070905/method_args-0.0.2.zip Try it out and then go sit outside in the cool grass, under the warm sun, and dream about how nice it would be to use arguments instead of params. We could even keep params around (at no extra speed cost and not depreciated) for those who enjoy typing. def show(id) @product = Product.find(id) render end The extension is a mere 160 lines of C code. It runs quickly and it seems to work rather well. Bob Hutchison wrote: > Another dissenting voice... I will not/cannot avoid the use of the > params object in some of my applications. So, please, no deprecation. > I don't care if Merb supported controller parameters or not, in > principle. I doubt I'd ever use them, I prefer to look at the params > object as an input data thing that needs to be inspected rather > carefully. On the other hand, Merb is still mostly light and easy to > understand, and starts very quickly -- it would be sad to see this end. Bob, in what way are you using params? Why can't you avoid it? I think you are not thinking about this correctly. ry _______________________________________________ Merb-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/merb-devel
