| Nikki Locke <nikki@trumphurst.com>: Aug 14 10:18PM Available C++ Libraries FAQ URL: http://www.trumphurst.com/cpplibs/ This is a searchable list of libraries and utilities (both free and commercial) available to C++ programmers. If you know of a library which is not in the list, why not fill in the form at http://www.trumphurst.com/cpplibs/cppsub.php Maintainer: Nikki Locke - if you wish to contact me, please use the form on the website. |
| "R.Wieser" <address@not.available>: Aug 14 10:36AM +0200 Manfred, > > > runtime implementations in the same process space > > Uhmmm. Not quite, but somewhat ? > In fact this seems to be the case, from your replies below. Your reading comprehension fails you I'm afraid. [quote-of-quote] that object might be written in A LANGUAGE OTHER THAN vc++" [/quote] (upper-casing mine) As far as I can tell that seems to indicate that there is a chance that the other part MIGHT be C++ too, but could easily be something else. > I don't think there is a way defined by the language (the standard > does not define an ABI), Lol. You're barking up the wrong tree there. I do not, and have never done so, ask for the language to deliver me an ABI, I'm trying to *find the tools* the language has to create my own. > It is worth recalling that there are very good reasons for which > you /cannot/ create a COM object with new, even if it is a C++ > object, Your reading comprehension fails you again. I've never said I wanted to create a COM object (and in retrospect mentioning VisualBasic as a language the external object could be written in was a bit of a mistake on my side), I said I wanted the *METHOD CALLS* to be COM alike. With me *specifically* describing that that, *from my very first post on*, ment I wanted the 'this' reference/pointer/whatever delivered (as in, to the external object) as the first argument. > > Than you have a *big* problem on your hands, as I *can't say* > > what is on the other end. > *I* don't have any problem, it looks like you have. I don't have a problem, as I know exactly what I'm after. Heck, I even penned it down a number of times now ! The only problem I have is that I do not know enough of the VC++ language to pick out the right commands for it. And thats where *you* where supposed to come in. The *problem* is that although you have offered yourself to help, you are seemingly either incapable or even not really willing to do so. And before you now blow your top, let me explain: Besides complaining about how my choices are all wrong and repeatedly requesting (demanding?) my code while ignoring what you already got, you have done *zero* in regard to pointing me to possible better solutions. And *thats* (pointers) is all I'm here for. With those I can investigate what they do and in the end *make my own choice* to which one I want to implement. I'm *definitily not* here for you to dictate what I need to write. So far I have indulged you in the hope you would come to some conclusion I could use. But as you seem to be incapable/unwilling of doing so, I'm going to end our conversation here. Someone earier in this thread said "you get what you pay for". Boy, did I get my full pound! :-(( Regards, Rudy Wieser P.s Compare your method of helping with the way Kalle does it. I think you can learn a lot from that/him. -- Origional mesage: Manfred <invalid@invalid.add> schreef in berichtnieuws ompdou$44e$1@gioia.aioe.org... > > [Quote=me] > > I'm calling an external (to the VC++ program) object (stored in a > > dynamically loaded DLL) which methods are based on the COM model, meaning > > [/Quote] > >> which would be trouble (it is undefined behaviour at best). > > If you know a better (and ofcourse defined by the language) way to call to > > an external object (by way of a pointer table) I'm willing (understatement) > a Microsoft compiler, and thus they are not portable. > >> The question is if it works by coincidence or because it is correct. > > :-) If, as Kalle, mentions it, the vtable structure has never been defined > > the conclusion is rather simple: its by sheer coincidence -- even though the > >> It is not clear if you are trying to destroy an object by explicitly > >> calling its destructor, which could also be trouble. > > Please re-ead the initial post of this thread. That is what this thread is > > all about. Can I do it (call the, as virtual declared, destructor and > > access an external object) ? What "gotyas" do I need to be aware of ? > > But as it turns out vc++ does not allow me to do so, as it refuses, even for > >>> You already got the vc++ end. Anything wrong with it ? How ? > >> It depends on what is on the other end, > > Than you have a *big* problem on your hands, as I *can't say* what is on the > > other end. > *I* don't have any problem, it looks like you have. > > As mentioned, it might be written in vc++, but even than it might be from > > defining the ABI. > > Ofcourse, I've already created an ABI. But if you have a good reason to > > change the vc++ side (and reference to how it *should* be done!) than again, > >> It's not poteto potato. The 'this' pointer (not reference) is passed > >> by the C++ implementation, > > So when I use it to refer to a classes method ("MyObject->Destructor") its > This shows confusion about what pointers are. > >> you should make clear what is the ABI specified by your implementation > > I already did. Several times. Starting with the example call posted in > > the initial message of my previous thread and repeated thruout both the > > threads > > As a reference, see the first paragraph in my first quote in this message. |
| Manfred <noname@invalid.add>: Aug 14 06:02PM +0200 On 8/14/2017 10:36 AM, R.Wieser wrote: > Manfred, <barking snipped> > So far I have indulged you in the hope you would come to some conclusion I > could use. But as you seem to be incapable/unwilling of doing so, I'm going > to end our conversation here. Fine with me, you managed to land into my killfile. |
| You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to comp.lang.c+++unsubscribe@googlegroups.com. |
No comments:
Post a Comment