On Mon, 2009-10-26 at 21:35 +0100, Federico Di Gregorio wrote: > Il giorno lun, 26/10/2009 alle 16.21 -0400, Jonathan Pryor ha scritto: > > In this case, instead of using a single regex parameter I would instead > > suggest following the EntityInterfaces and MemberExposedAttributes > > option by using comma-separated names. > > > > In a truly ideal world we'd replace Parameters.cs/etc. with Mono.Options > > or NDesk.Options [0], which would allow you to do "DbMetal -entity A > > -entity B -entity C ...", using '-entity' for each type you wanted to > > provide. > > Uh?! I always supposed such "big" changes were to be avoided. Can we > really send a patch that removes all the custom cruft and replace it > with Mono.Options?
For the love of $deity, please. :-) The more important question isn't so much "how big is the change," as much as "does this regress anything?" Alas, we don't have very many DbMetal tests, and it already looks like DbMetal has been broken in some important ways (see other messages on this list). Still, I'd love to get a better option parser in here. - Jon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DbLinq" 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/dblinq?hl=en -~----------~----~----~----~------~----~------~--~---
