Hi Terry, >After playing around with translators and getting args[0]->??? to work in my >test provider I have a question that is nagging me. If conninfo_t is to be a >common typedef to be used by any provider shouldn't it be contained in a >common .d file instead of something like iscsi.d or mpi.d? >
Indeed it should. Currently we have no way of specifying dependencies between library files as you would need to do here; we just compile them in the order in which we find them. However, I've just about finished implementing a library dependency mechanism which will allow you to do this and I hope to get that back in the next few weeks. >There also seems to be even a more greater name clashing situation that I >wonder how to handle. That is how do I assure myself that the typedefs >private to mpi.d like the ones used for the mpi translators will not clash >with someone elses? Is there a naming convention or registry I should be >adhering too? > Others may want to comment here but I think it sensible that you prefix names with the provider name or some common pattern that makes sense within that provider. Jon. _______________________________________________ dtrace-discuss mailing list [email protected]
