Hi All, I'm trying not to get sucked into this debate, but I will say one thing: if you feel really strongly about changing something, make a plugin with the behavior, promote it to the mailing list, and if it gets wide usage *and* proves itself in practice to the DM devs *then* try to push for the DataMapper API to be changed.
At this stage of DM's development, changes that alter the core API -- potentially affecting deployed code -- should only be accepted after proving themselves as plugins first anyway. I mean, this is a tiny amount of we're talking about. Given how long this threads is I bet by now the plugin could've been written several times with the amount of time spent trying to convince others of it's advantages. I say write the code and let it speak for you ;) Dan (dkubb) P.S. I can't resist throwing in my two cents: I agree with Sam. However, I'm not going to attempt to add anything new, because really at this stage I think all the important pros/cons have been discussed already. Besides, my thoughts can be nicely summed up by the following: http://is.gd/a0QH --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
