Thats no problem, there is no naming conflict.
BM is scope based, so you could still access both by brl.math3d.xx and leadwerks.math3d.xx
But what you can't do is name a type the same as a module and in the specific case of the core types (object, string and all the numeric types), name a module like a type.
With all other, fully BM based types within BRL and PUB, there is no problem, those aren't "hardcoded". Only the types etc within brl.blitz are reserved from I've seen (and had to find out the hard way ^^) so far.
BM is scope based, so you could still access both by brl.math3d.xx and leadwerks.math3d.xx
But what you can't do is name a type the same as a module and in the specific case of the core types (object, string and all the numeric types), name a module like a type.
With all other, fully BM based types within BRL and PUB, there is no problem, those aren't "hardcoded". Only the types etc within brl.blitz are reserved from I've seen (and had to find out the hard way ^^) so far.