From: <dg...@ni...> - 2006-08-11 16:55:43
|
Quoting Andreas Kupries <and...@ac...>: > I prefer the former actually, keep comm itself focused on the communication > aspects, and use the proposed package for the linkage to useful execution > environments. I'm not a comm user, and I haven't carefully read all of these messages, but at arms length it sure looks like you're inventing a set of commands that would be good additions to the comm package itself, rather than another separate package. I think that means I'm agreeing with Hemang. That said, if more direct experience indicates this really should be a separate package from "comm", then give it a name separate from "comm" as well. This nested namespace stuff is anti-modular. Just IMHO. DGP |