Federico Di Gregorio dichiarò: > 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?
Mh, option parsing in DbMetal is already broken, as you cannot pass an absolute unix path for the source DBML file or it will be interpreted as an option: > $ mono --debug DbMetal.exe -code:output.cs /home/test/input.dbml > DbLinq Database mapping generator 2008 version 0.19 > for Microsoft (R) .NET Framework version 3.5 > Distributed under the MIT licence (http://linq.to/db/license) > > Parameter home/test/input.dbml does not exist Hopefully migrating to a more common option framework will solve these issues. Regarding the original patch, I've used a single regex as these can also express choice with grouping and the alternation operator "(Foo)|(Bar)". If you think it's more sensible to use simple class names separated with commas (or specified in multiple repeated options) I'll quickly rework the patch. -- Emanuele Aina Studio Associato Di Nunzio e Di Gregorio http://dndg.it/ Via Maria Vittoria, 2 10123 Torino - Italy --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
