I've been thinking a bit about writing a JSM for validating arguments coming
into a function.
The first part would be the set of assertion functions:
* a non-empty string
* a whole number
* a positive number
* a non-negative number
* a function
* instanceof
* typeof
* member of
On Wed, May 14, 2014 at 05:46:23PM -0700, Tim Abraldes wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Build took 41:02 with these options:
> ac_add_options --enable-chrome-format=flat
> ac_add_options --disable-optimize
> ac_add_options --enable-debug-symbols
> ac_add_options
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Build took 41:02 with these options:
ac_add_options --enable-chrome-format=flat
ac_add_options --disable-optimize
ac_add_options --enable-debug-symbols
ac_add_options --disable-crashreporter
ac_add_options --disable-updates
ac_add_options -
On 2014-05-13, 9:01 PM, Rik Cabanier wrote:
On Tue, May 13, 2014 at 3:16 PM, Ehsan Akhgari mailto:ehsan.akhg...@gmail.com>> wrote:
...
That is not the point of this attribute. It's just a hint for
the author
so he can tune his application accordingly.
requestAutocomplete [1], for those unfamiliar with the API, is a proposed
addition to the HTML spec where browser vendors show a dialog to users
for populating payment and address fields on a page. Payment and
address autocomplete profiles can be created by the user, where the
user fills in individ
5 matches
Mail list logo