Re: [macker-user] naming convention for classes implementing an interface
Brought to you by:
barredijkstra,
melquiades
From: Paul C. <can...@po...> - 2005-12-06 03:16:06
|
Hello again, Etienne! There is currently no good way of doing this. One of those features in the queue is to allow rules of the form "everything that matches X must / must not match Y," which is what you need. If there is a specific IFoo you want to write a rule for, you can do this (icky, but I believe it works): <access-rule> <deny> <from> <include filter="subtype-of" class="IFoo"/> <exclude class="**.*FooImpl"/> </from> <to class="void"/> </deny> </access-rule> If, however, you want this rule to apply generically to every IFoo, IBar, and IBaz (with FooImpl, BarImpl, and BazImpl respectively), you're out of luck. Hope this helps, at least a little.... BTW, if anybody on the list feels like making a donation to push the next version of Macker into more active development, I certainly wouldn't object. Cheers, Paul On Dec 2, 2005, at 5:28 PM, Etienne Studer wrote: > Hi Paul > > How can I define a rule that says: > > all implementations of interface IFoo must match a class name > '.*FooImpl' > > Your kind help would be once again very much appreciated!! > > --Etienne > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through > log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD > SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Macker-user mailing list > Mac...@li... > https://lists.sourceforge.net/lists/listinfo/macker-user > > Macker home page: http://innig.net/macker/ > _________________________________________________________________ Piano music podcast: http://inthehands.com Other interesting stuff: http://innig.net |