1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179
// // DO NOT EDIT. THIS FILE IS GENERATED FROM ../../../dist/idl/mozIMozIntl.idl // /// `interface mozIMozIntl : nsISupports` /// /// ```text /// /** /// * This is a set of APIs that are of general usefulness for user interface /// * internationalization. /// * /// * They're all in various stages of the standardization process through /// * ECMA402, so they are exposed to privileged content only but are written /// * in the way to allow for easy migration to standard Intl object once /// * the appropriate stage of the ECMA402 is achieved. /// * /// * The exact structure of the code is a little bit complex because of that: /// * /// * 1) The core is in SpiderMonkey together with other Intl APIs /// * /// * This allows us to write the code once, stick to the spec language /// * of the proposal, reuse our ICU bindings in Spidermonkey and use /// * the code to inform us on refining the spec proposal for the given API itself. /// * /// * 2) The MozIntlHelper API exposes the SpiderMonkey APIs /// * /// * This helper API allows attaching the new APIs on any regular object. /// * /// * 3) The MozIntl API provides the access to those APIs /// * /// * This API exposes the actual functionality and wraps around the MozIntlHelper /// * lazily retrieving and setting the accessors. /// * On top of that, the API also binds additional functionality like using /// * current application locale by default, and fetching OS regional preferences /// * for date time format. /// */ /// ``` /// // The actual type definition for the interface. This struct has methods // declared on it which will call through its vtable. You never want to pass // this type around by value, always pass it behind a reference. #[repr(C)] pub struct mozIMozIntl { vtable: *const mozIMozIntlVTable, /// This field is a phantomdata to ensure that the VTable type and any /// struct containing it is not safe to send across threads, as XPCOM is /// generally not threadsafe. /// /// XPCOM interfaces in general are not safe to send across threads. __nosync: ::std::marker::PhantomData<::std::rc::Rc<u8>>, } // Implementing XpCom for an interface exposes its IID, which allows for easy // use of the `.query_interface<T>` helper method. This also defines that // method for mozIMozIntl. unsafe impl XpCom for mozIMozIntl { const IID: nsIID = nsID(0x7f63279a, 0x1a29, 0x4ae6, [0x9e, 0x7a, 0xdc, 0x96, 0x84, 0xa2, 0x35, 0x30]); } // We need to implement the RefCounted trait so we can be used with `RefPtr`. // This trait teaches `RefPtr` how to manage our memory. unsafe impl RefCounted for mozIMozIntl { #[inline] unsafe fn addref(&self) { self.AddRef(); } #[inline] unsafe fn release(&self) { self.Release(); } } // This trait is implemented on all types which can be coerced to from mozIMozIntl. // It is used in the implementation of `fn coerce<T>`. We hide it from the // documentation, because it clutters it up a lot. #[doc(hidden)] pub trait mozIMozIntlCoerce { /// Cheaply cast a value of this type from a `mozIMozIntl`. fn coerce_from(v: &mozIMozIntl) -> &Self; } // The trivial implementation: We can obviously coerce ourselves to ourselves. impl mozIMozIntlCoerce for mozIMozIntl { #[inline] fn coerce_from(v: &mozIMozIntl) -> &Self { v } } impl mozIMozIntl { /// Cast this `mozIMozIntl` to one of its base interfaces. #[inline] pub fn coerce<T: mozIMozIntlCoerce>(&self) -> &T { T::coerce_from(self) } } // Every interface struct type implements `Deref` to its base interface. This // causes methods on the base interfaces to be directly avaliable on the // object. For example, you can call `.AddRef` or `.QueryInterface` directly // on any interface which inherits from `nsISupports`. impl ::std::ops::Deref for mozIMozIntl { type Target = nsISupports; #[inline] fn deref(&self) -> &nsISupports { unsafe { ::std::mem::transmute(self) } } } // Ensure we can use .coerce() to cast to our base types as well. Any type which // our base interface can coerce from should be coercable from us as well. impl<T: nsISupportsCoerce> mozIMozIntlCoerce for T { #[inline] fn coerce_from(v: &mozIMozIntl) -> &Self { T::coerce_from(v) } } // This struct represents the interface's VTable. A pointer to a statically // allocated version of this struct is at the beginning of every mozIMozIntl // object. It contains one pointer field for each method in the interface. In // the case where we can't generate a binding for a method, we include a void // pointer. #[doc(hidden)] #[repr(C)] pub struct mozIMozIntlVTable { /// We need to include the members from the base interface's vtable at the start /// of the VTable definition. pub __base: nsISupportsVTable, /* jsval getCalendarInfo ([optional] in jsval locales); */ /// Unable to generate binding because `native type JS::Value is unsupported` pub GetCalendarInfo: *const ::libc::c_void, /* jsval getDisplayNames ([optional] in jsval locales, [optional] in jsval options); */ /// Unable to generate binding because `native type JS::Value is unsupported` pub GetDisplayNames: *const ::libc::c_void, /* jsval getLocaleInfo ([optional] in jsval locales); */ /// Unable to generate binding because `native type JS::Value is unsupported` pub GetLocaleInfo: *const ::libc::c_void, /* jsval createDateTimeFormat ([optional] in jsval locales, [optional] in jsval options); */ /// Unable to generate binding because `native type JS::Value is unsupported` pub CreateDateTimeFormat: *const ::libc::c_void, } // The implementations of the function wrappers which are exposed to rust code. // Call these methods rather than manually calling through the VTable struct. impl mozIMozIntl { /// `jsval getCalendarInfo ([optional] in jsval locales);` const _GetCalendarInfo: () = (); /// `jsval getDisplayNames ([optional] in jsval locales, [optional] in jsval options);` const _GetDisplayNames: () = (); /// `jsval getLocaleInfo ([optional] in jsval locales);` const _GetLocaleInfo: () = (); /// `jsval createDateTimeFormat ([optional] in jsval locales, [optional] in jsval options);` const _CreateDateTimeFormat: () = (); }