neat. Ok I'm afraid that the Inline route isn't going to be robust enough. I also would like to keep the DLL external to Perl so that it can be accessed by other languages. Attached is the header file. As you can see it is not an example of the best C++ skills in the world. The main gist of this DLL is to interace with the IIS metabase without the use of ADSI. I also don't want to go the Win32::API route as it seems a bit kludgy to me. Albeit, it may be the only way.
Thoughts/comments/snide remarks? |> -----Original Message----- |> From: [EMAIL PROTECTED] |> [mailto:[EMAIL PROTECTED]]On Behalf Of |> Sisyphus |> Sent: Tuesday, January 14, 2003 9:08 PM |> To: [EMAIL PROTECTED] |> Subject: Re: H2XS and C++ |> |> |> |> ----- Original Message ----- |> From: "Floyd Russell" <[EMAIL PROTECTED]> |> To: <[EMAIL PROTECTED]> |> Sent: Wednesday, January 15, 2003 12:14 PM |> Subject: H2XS and C++ |> |> |> > Could/would anyone be willing to help be get a c++ dll I recently wrote |> > h2xs'ed into a proper Perl module? I don't really even know |> where to start |> > reading - since everything I seem to come across is geared toward *nix. |> > |> > Thanks, |> > Floyd |> > |> > |> |> Can you get perl to successfully access the function(s) using the |> Inline::CPP module ? |> |> If you can, then you're home and hosed, because Inline::CPP will have |> generated the XS code for you and it's a fairly simple (though slightly |> messy) matter to then assemble the files so that a module (which exports |> those functions) can be built. |> |> If, like me, you find 'perlguts' to be about as appealing as |> sheepguts, then |> I would definitely start with Inline::CPP. |> Actually, I think it might be simpler again with Inline::C, so if writing |> the source in C is an option, I would recommend doing just that. |> Either way, |> the Inline mailing list (see http://lists.perl.org ) is there to help. |> |> Depending on the data types, you might find there are some |> bridges to cross |> before your code will work with Inline::CPP or Inline::C - but |> those will be |> bridges that would have to be crossed no matter how you approach the |> problem. |> |> I'm certainly prepared to help with the final (easy) step of using the |> auto-generated XS code to create a module. |> |> You might also find "Extending and Embedding Perl" by Tim |> Jenness and Simon |> Cozens useful. |> |> As one alternative, I guess that if working with Inline::C or |> Inline::CPP is |> unpalatable to you, then, since you already have the dll, you |> could access |> those functions by using Win32::API. I think that's viable, but I can't |> offer any help (owing to dumbness). |> |> If you can provide information on the argument and return types |> of the dll |> functions then others on this list might be able to help with |> the Win32::API |> calls that are required. |> |> Cheers, |> Rob |> |> |> |> _______________________________________________ |> Perl-Win32-Users mailing list |> [EMAIL PROTECTED] |> To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs |>
IMSAdmin.h
Description: Binary data
