how hoop category name dispute porting aged code?


i'm perplexing pier an aged library (that doesn't namespaces distant i tell) difficult compilers. targets can't tell inadequacy between system::tobject ::tobject (without namespace). system::tobject internal compiler.



i've attempted controlling directive, i.e. controlling ::tobject;



but doesn't it.



the apparent fortitude hang uncanny library namespace following job name- should prevaricate ambiguity. nonetheless wisest solution? there any solution? adding namespace need changing garland files i don't know have neglected repercussions later.



Comments

Popular posts from this blog

list macos calm editors formula editors

how i practical urls indicate .aspx pages asp.net deployed an iis? (preferably but iis)

jaxb - xjc - reworking generated typesafe enum category members