Comments on: All-in-one cookie function

By: Best-of-the-Web 4 | davblog: webdev and stuff

Best-of-the-Web 4 | davblog: webdev and stuff — Mon, 03 Jan 2011 17:46:03 +0000

[...] All-In-One cookiefunction – Eine Javascript-Cookie-Funktion die an Einfachheit kaum noch zu unterbieten ist. [...]

By: Ash

Ash — Thu, 29 Apr 2010 05:53:29 +0000

Thanks Dan (and thanks for pointing out exactly where the problem was.) I’ve fixed that now.

Your wee comment reminds me I should get off my butt and finish another blog post..

By: Dan Beam

Dan Beam — Tue, 27 Apr 2010 18:04:26 +0000

Sorry, forgot to mention, the type’s in the file you’ve linked to: http://hexmen.com/js/cookie.js.

Assuming you understood, but just making sure.

By: Dan Beam

Dan Beam — Tue, 27 Apr 2010 18:02:46 +0000

Hey Ash, there’s a little error in your doc – first line, says “cooke”. Just letting you know.

By: Tim Down

Tim Down — Sun, 24 Jan 2010 13:19:38 +0000

OK, I see now.

I am constantly frustrated when designing APIs in JavaScript that lend themselves naturally to the kind of overloading you can do in languages like Java or C#. The options are:

1. Write several functions with slightly different names to deal with all the possibilities. Pros: clean to implement. Cons: bloats the API, hard to use.

2. One function with overloading. Pros: quite simple to use. Cons: still requires remembering/looking up combinations of arguments that may be passed, and requires code in the implementation to check number and types of the arguments.

3. One function that accepts a single object whose properties are just the arguments the caller requires. Pros: easy to use, flexible. Cons: requires extra code in the implementation to check properties of the object passed in, introduces possibility of error by mistyping property names in the calling code.