Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?
 
PerlMonks  

Re^2: Win32::API::Struct: Pointers of Pointers

by esskar (Deacon)
on Jun 29, 2006 at 05:46 UTC ( #558221=note: print w/replies, xml ) Need Help??


in reply to Re: Win32::API::Struct: Pointers of Pointers
in thread Win32::API::Struct: Pointers of Pointers

No, the structure is ENCRYPTION_CERTIFICATE_HASH_LIST and PENCRYPTION_CERTIFICATE_HASH_LIST is already a pointer. So, PENCRYPTION_CERTIFICATE_HASH_LIST* is a mointer of pointer.

Knowing a lot about C and C++ programming (mainly under Windows), your suggestion can not work correctly.
  • Comment on Re^2: Win32::API::Struct: Pointers of Pointers

Replies are listed 'Best First'.
Re^3: Win32::API::Struct: Pointers of Pointers
by runrig (Abbot) on Jun 29, 2006 at 19:03 UTC
    Knowing a lot about C and C++ programming (mainly under Windows), your suggestion can not work correctly.

    I'm just going by the principle that the documentation is not always right, and it doesn't hurt to try something else. The argument description says that it is a pointer to a structure. The "*" in the function syntax suggests it's a pointer to a pointer to a structure. One of those is wrong. If you've implemented this in C or C++ and you know for sure, then nevermind.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://558221]
help
Chatterbox?
[Corion]: ambrus: Yeah, that's what I think as well. But you give me an idea, maybe I should start with implementing the timer, as that should be far simpler and with fewer edge-cases/nasty interaction than the file watcher
[ambrus]: You only provide the watcher part that tells when the handle is readable or writable, not the actual writing and reading.
[Corion]: ambrus: Hmmm. It makes sense that AnyEvent would implement the push_write itself, but I think I don't have a good idea of where the boundary between AnyEvent and the underlying event system lies... Implementing the timer should give me a better idea
[ambrus]: Corion: push_write is in the higher level abstraction of AnyEvent::Handle, not in the watcher
[Corion]: ambrus: Hmm - rereading Prima::File, that merrily coincides with what Prima does - it tells you "you can read", and you're supposed to read from the fh yourself. I thought it called you with the data already read, which would've been harder to integrate
[ambrus]: you just need an io watcher, created by &AnyEvent::Impl:: Whatever::io(...)
[Corion]: So after talking it through with you even while I'm still not entirely clear on where AE ends and my implementation begins, I think I understand that I only need to implement some smaller parts for each functionality I want to support.
[Corion]: Yeah... and you might even be able to mix and match additional functionality if you have additional async suppliers, like from a separate thread
[ambrus]: You hvae to be careful with the timer, because apparently Prima::Timer insists on being periodic, wheras AnyEvent::Impl:: Whatever::timer should give a one-shot timer watcher

How do I use this? | Other CB clients
Other Users?
Others perusing the Monastery: (6)
As of 2016-12-08 12:23 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    On a regular basis, I'm most likely to spy upon:













    Results (141 votes). Check out past polls.