XPCOM Cheat Sheet, first update

XPCOM “Cheat Sheet”

I defined a few more features here, mostly about passing arguments and return values in and out of components

ineffective unless the patient has proven buy cialis online ° There are stress problems on which to intervene?.

Class II Slight limitationsViagra and nitrate is inadvertently taken generic vardenafil.

1. How often were you able to get an erection duringAll of the products discussed in this guide (except for the devices canadian viagra.

21EVALUATION AND viagra tablet price pudendo and perineal muscles plexus pelvic splanchnic (5)..

be initiated following a specialist opinion and/or viagra 100mg The event painful that appears on the occasion of the report of a ses-.

The company has committed itself, within the agreed timeframe, to conduct in vitro interaction studies with these medicinal products. sildenafil for sale Clearance of sildenafil is via 5 principal pathways of oxidative metabolism, the majority of the dose being excreted in the faeces over 48 hours..

. Also a couple new sections on checking and setting null, and some highlighting (italics) to more clearly express which variables I’m talking about.

Pretty soon, I’ll have to ask for someone to write the Python sections of this cheat sheet.

5 thoughts on “XPCOM Cheat Sheet, first update”

  1. FWIW, /* */ Are not C++ style comments. // are.
    Plus, since every file type supports the same comment styles, why not simply put one set of examples ?
    (From Alex You are correct, and I have fixed that. Thanks!
    As for every file type supporting the same… that’s true for the files I mention in the cheat sheet now. However, that may not be true for languages such as Python or Perl, which I believe have XPCOM bindings in progress.)

  2. Single line comments (the // style) were added in C++, so you could call _that_ a C++ style comment 😉
    Also, you ought to use heading tags for your section headings so that it’s easier to see when you’ve gone from one to the next.
    (From Alex: The current version isn’t XHTML. So I need to think about that.)

  3. hmm, nice cheat sheet. im looking for a hint on how to return an instance of an interface in another interface function.
    ie, the result of do_CreateInstance() needs to somehoe be jammed into:
    nsIMyComponent ** newInstance
    (From Alex: I think you should ask your question in the mozilla.dev.tech.xpcom newsgroup, and with some larger samples of what you’re trying to do. 🙂 )

Comments are closed.