Actually there's never been a single problem with this issue (as far as BVM is concerned), mostly because trying to compete directly with the underlying host language by selling a simple wrapper is too stupid and weak for most people to even think of it. For the others, the BVM license has always been there to explictely forbid that extreme(ly stupid) use.
In fact your carefull use of the expression "came to light" is perfect. Indeed it only "raised the issue", but never had to face it. Generally speaking what really matters in the end is the use that is made of the available tools, and that's totally up to the tool user.
Nonetheless it's always beneficial for everybody to have a license that says clearly what you can and cannot do. As a counterexample, when writing BVM I wasn't even sure BRL would like that and I had to get in touch with them directly. And that's not always easy.
Sorry if I'm a bit BVM-centric here but I think it applies very well to any similar product anyway.
In fact your carefull use of the expression "came to light" is perfect. Indeed it only "raised the issue", but never had to face it. Generally speaking what really matters in the end is the use that is made of the available tools, and that's totally up to the tool user.
Nonetheless it's always beneficial for everybody to have a license that says clearly what you can and cannot do. As a counterexample, when writing BVM I wasn't even sure BRL would like that and I had to get in touch with them directly. And that's not always easy.
Sorry if I'm a bit BVM-centric here but I think it applies very well to any similar product anyway.