------ art_4206_29560565.1226386692902 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Lots of responses here. 1) I'd be in favor of an object-based API. I'll probably post tomorrow with some thoughts on that. I only provided the tuple-based API because already have it in all impls (except 1.9) and it already works. 2) I agree that there are potentially more powerful things that we *could* do. However, those things would take a lot of time to get right. This feature is simple and limited enough to be definitely supportable across implementations, and possible to nail down quickly and efficiently. What I specifically would like to avoid is a very long discussion about trying to get a perfect, large API to handle a superset of these features (such as full support for a locked-down AST), when the simple version would be extremely helpful all on its own. Hope that made sense, -- Yehuda On Tue, Nov 11, 2008 at 1:17 AM, Roger Pack <rogerpack2005 / gmail.com> wrote: > > I suspect that it isn't. I, for one, want to see as few libraries that > > are doing something like: > > > > case RUBY_ENGINE > > when 'mri' > > when 'jruby' > > ... > > end > > Oh I'm favor of it--I would however suggest that allowing for > "docstrings" and/or parse trees of methods would be even more powerful > overall :) > > Stay well. > - > > -- Yehuda Katz Developer | Engine Yard (ph) 718.877.1325 ------ art_4206_29560565.1226386692902 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Lots of responses here.<div><br></div><div>1) I'd be in favor of an object-based API. I'll probably post tomorrow with some thoughts on that. I only provided the tuple-based API because already have it in all impls (except 1.9) and it already works.</div> <div><br></div><div>2) I agree that there are potentially more powerful things that we *could* do. However, those things would take a lot of time to get right. This feature is simple and limited enough to be definitely supportable across implementations, and possible to nail down quickly and efficiently.</div> <div><br></div><div>What I specifically would like to avoid is a very long discussion about trying to get a perfect, large API to handle a superset of these features (such as full support for a locked-down AST), when the simple version would be extremely helpful all on its own.</div> <div><br></div><div>Hope that made sense,</div><div><br></div><div>-- Yehuda<br><br><div class mail_quote">On Tue, Nov 11, 2008 at 1:17 AM, Roger Pack <span dir tr"><<a href ailto:rogerpack2005 / gmail.com">rogerpack2005 / gmail.com</a>></span> wrote:<br> <blockquote class mail_quote" style argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class h2E3d">> I suspect that it isn't. I, for one, want to see as few libraries that<br> > are doing something like:<br> ><br> > case RUBY_ENGINE<br> > when 'mri'<br> > when 'jruby'<br> > ...<br> > end<br> <br> </div>Oh I'm favor of it--I would however suggest that allowing for<br> "docstrings" and/or parse trees of methods would be even more powerful<br> overall :)<br> <br> Stay well.<br> <font color 888888">- br> <br> </font></blockquote></div><br><br clear ll"><br>-- <br>Yehuda Katz<br>Developer | Engine Yard<br>(ph) 718.877.1325<br> </div> ------ art_4206_29560565.1226386692902--