labofsahil/github-event-dataset-2012 huggingface dataset:
That's a copy-past from the RectBivariateSpline class.

Am 25.02.2012 15:13, schrieb Pauli Virtanen:
>> +                            'elements as u')
>> +        if not v.size == r.shape[1]:
>> +            raise TypeError('v dimension of r must have same number of '
>> +                            'elements as v')
>> +        if pole_continuity[1] is False and pole_flat[1] is True:
>> +            raise TypeError('if pole_continuity is False, so must be pole_flat')
>> +        if pole_continuity[0] is False and pole_flat[0] is True:
>> +            raise TypeError('if pole_continuity is False, so must be pole_flat')
>> +        r = np.ravel(r)
>> +        nu,tu,nv,tv,c,fp,ier = dfitpack.regrid_smth_spher(iopt,ider,u.copy(),
>> +                                                          v.copy(),r.copy(),r0,
>> +                                                          r1,s)
>> +        if not ier in [0,-1,-2]:
>> +            message = _spfit_messages.get(ier, 'ier=%s' % (ier))
>> +            warnings.warn(message)
>> +            raise ValueError()
> 
> Here the message should be given to ValueError, rather than in the warning.
> 
> --- 
> Reply to this email directly or view it on GitHub:
> https://github.com/scipy/scipy/pull/117/files#r488632
лень это исправлять. Старый код. В новом я все так делаю.
lame spacing comment: should be a space between the `=>` and referenced item.
Please inline the variable "bases".
I think that might be a bad idea to stuff the id in the context because other api's don't need the id. (ie detail/index calls for instance). And new methods that others add in the future can not depend on an id being available from the context in all cases.
No need for this line, super class already does this.
that's right, this is mostly a performance optimisation.
Should we throw an exception if no migrators are found ?
good catch. I have been having  a hard time testing this.


On Sat, Nov 10, 2012 at 5:35 PM, Andrew <notifications@github.com> wrote:

> In requests/auth.py:
>
> > +            return response
> > +
> > +        request = response.request
> > +        # initial auth header with username. will result in challenge
> > +        auth = 'NTLM %s' % ntlm.create_NTLM_NEGOTIATE_MESSAGE("%s\\%s" % (self.domain,self.username))
> > +        request.headers[auth_header] = auth
> > +
> > +        # we must keep the connection because NTLM authenticates the connection, not single requests
> > +        request.headers["Connection"] = "Keep-Alive"
> > +
> > +        request.send(anyway=True)
> > +        response2 = request.response
> > +
> > +        # this is important for some web applications that store authentication-related info in cookies (it took a long time to figure out)
> > +        if response2.headers.get('set-cookie'):
> > +            headers['Cookie'] = response2.headers.get('set-cookie')
>
> I understand where response2.headers comes from, but it doesn't look like
> the headers in headers['Cookie'] is defined anywhere. Again, I might be
> missing something, though.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/kennethreitz/requests/pull/934/files#r2091941>.
>
>



-- 
-Ben Toews
Why do you need a timestamp on a static picture reference?
That is technically correct, but it's not actually the point. Acronymns in classes must be CamelCased, so `SQL` must be written as  `Sql`. It will be confusing and irritating if we set an example that it's OK to capitalise acronyms in the namespace and not in the class naming. It doesn't have to be a rule, just set by example and it makes things a lot easier for adoption since there is consistency in the flow. FYI we chose not to impose the rule on the namespace because PSR-0 had already been out for a long time and some had adopted all lowercase vendor names. As a result, imposing a rule on namespace would have meant either those projects would have to create a BC break in order to adopt PSR1/2 or comply with only part. The best compromise was to just leave the vendor naming alone. This does not mean we should not set an example that is consistent with the naming of classes. `DrakPHP\Dumper\PhpDumper` for example is going to look stupid because of the inconsistency. For this reason, let's keep camel casing standards consistent within our code examples.
@Seldaek Don't existing libraries have to break BC anyway when they want to add this interface? The string vs int argument seems invalid then.
@jsloane indeed, I removed some of the plug-ins that we weren't using. We can always add it in later on.
@bp323 Can we remove this change? It seems like nothing else changed in this file.
please no different swig flags - you can edit your .config or write a  .config-local to override the flags locally
I find this description a little misleading - what do you think of something like "checks if a given transition is possible"?
I think the conditional about future dates just over complicates here. If I ask for reports 
between date X and date Y, why does it matter if day Y is 10 years in the future?
the reports result is still accurate.
@tlubz I originally had it that way but @shuqunzhang changed it because "enabled isn't an attribute of the experiment itself but in the db."

I'm not too sure about it either way. On one hand, `enabled?` has its behavior influenced by `active?` and `collecting?`, so it's misleading to treat it as a normal attribute. On the other hand, you certainly can treat it normally at certain times (when active == true and collecting == true). Thoughts?
WT_VERBOSE_VOID should probably be WT_VERBOSE_ERR; I think some of the other WT_VERBOSE_XXX calls are wrong, too.
why not "url", like we have it in some other places, I thought?
Just do an `assertEquals` with an array, it's easier to understand.
How about using ``$packages[$firstPackage->getUniqueName()]->name`` instead of ``$packages[$firstPackage-...niqueName()]->getName()``. There are some issues with ``getName()`` and APC-enabled PHP versions (see https://bugs.php.net/bug.php?id=61384).
Rspec is how we should all live our lives.  Rspec is the Buddha.

Sent from my iPhone

On Sep 17, 2012, at 19:49, beverlynelson <notifications@github.com> wrote:

In test/unit/user_test.rb:

> @@ -0,0 +1,7 @@
> +require 'test_helper'
> +
> +class UserTest < ActiveSupport::TestCase
> +  # test "the truth" do
> +  #   assert true
> +  # end
> +end

Rspec is absolutely my preference. I believe
@Stubby<https://github.com/Stubby>feels the same way on this for
testing.

—
Reply to this email directly or view it on
GitHub<https://github.com/RubyBay/ruby-resources/pull/9/files#r1624889>.
Comment on previous line
can you remove this bit of extra whitespace please.
Hab ich mir auch überlegt... war einfach zu faul ;-)

Aber ich mach mich schnell dahinter, kann ja nicht son ne sache sein...  :godmode:
(На сколько я понимаю из названий таблиц)
Таблица order не нужна, лучше назовите так order_details.
CREATE TABLE order (
id int(5) NOT NULL AUTO_INCREMENT,
id_user int(5) NOT NULL,
id_dish int(5) NOT NULL,
date date NOT NULL,
num int(5) NOT NULL,
PRIMARY KEY (id)
)
Я писал об этом вчера
Suunnilleen just se mitä `every?` tekee:

~~~clojure
(every? (set->predicate (:awards book)) awards)
~~~
After encountering linker errors with the static version of GLFW, I added a conditional that assumes that the static version of GLFW is used on Windows because it is more common.  This could be further improved by a more explicit check to see if the static version is being used.
Okay, then thumbnail_attribute definitely makes sense.

I can see why you chose ``thumbnail_file`` for ``Video``; I'm not entirely convinced that it's the right path. Generally speaking, people will be much more interested in the file itself than the url returned from vidscraper, so it's to our advantage to make that attribute name as short as possible. ``thumbnail`` also seems like a more intuitive name. If we want to draw a bigger distinction between the two fields, perhaps we could rename ``thumbnail_url`` to ``remote_thumbnail_url`` instead? That would make the purpose of that field clearer, as well.
tinymce_wysiwyg_support.pt is not included in collective/tinymce, and it looks like the upgrade_tinymce.sh script will not clobber it. Thanks for the reminder though.
The path it's splitting is the one given over the wire, not necessarily a local filesystem path, which I've assumed uses forward slashes as directory separators. Do Windows clients request paths with backslash separators?
Why don't you just call this `wrapInCDATA` also using a more universal variable name like `$data`?
This function is not suitable for parameters only.
looks great good job
А вот и нашёлся нормальный брат уродца `feed`. 

Вообще этот метод не нужен. Когда пишешь `has_many :posts`, то автоматически генерится метод `posts`, которые делает то же самое.
Tell that to the pycharm automatic import :P
*Login using your existing account:*
As you noticed already, we cannot remove this yet.
I would say that sounds right, Conor. Easier just to make it a separate page and come back to same page edits for the final release.
You should probably use `#{}` string interpolation here.
2012/11/28 csware <notifications@github.com>

> In src/Resources/TortoiseProcENG.rc:
>
> > @@ -747,11 +747,13 @@ BEGIN
> >      PUSHBUTTON      "Clear",IDC_RESIZABLEHISTCLEAR,243,93,50,14
> >      LTEXT           "Authentication data",IDC_AUTHHISTORY,7,120,226,8
> >      PUSHBUTTON      "Clear",IDC_AUTHHISTCLEAR,243,118,50,14
> > -    GROUPBOX        "Action log",IDC_STATIC,7,148,286,62
>
> Right now TortoiseGit leaves hundreds/thousands of temp-files behind on
> normal use - not nice. So I think we should do this (we could increase the
> time to one week maybe). If files are still open, we do not delete them.
>
Why generate so much temp-files?

> TortoiseSVN does the same w/o any users reporting problems.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/TortoiseGit/TortoiseGit/pull/2/files#r2247108>.
>
>
felt dirty :)
Ah, like Haskell's `@`. Thanks, @satyr. That is the perfect counter-argument.
if input is list, tuple or dict (see line 20), then run sifter-python
Looks like github filtered out the html element from my earlier comment :(

I was referring to parent/relativePath element, which just points submodule to directory containing parent pom.xml if it's likely to be close by. Generally, this is just "..".
I thought about removing that flag and then leaving the option up to the
path filter, but then the pathfilter needs to do figure out if a path is a
directory which requires a FileSystem and config.
On Nov 29, 2012 2:01 PM, "Raghu Angadi" <notifications@github.com> wrote:

> In core/src/main/java/com/twitter/elephantbird/util/HdfsUtils.java:
>
> > +  /**
> > +   * Recursively walk a path, adding paths that are accepted by filter to accumulator
> > +   *
> > +   * @param path root path to begin walking, will be added to accumulator
> > +   * @param filter filter to determine which paths to accept
> > +   * @param conf hadoop conf
> > +   * @param accumulateDirectories whether or not to accumulate directories
> > +   * @param accumulator all paths accepted will be added to accumulator
> > +   * @throws IOException
> > +   */
> > +  public static void collectPaths(Path path, PathFilter filter, Configuration conf,
> > +      boolean accumulateDirectories, final List<Path> accumulator) throws IOException {
> > +
> > +    walkPath(path, filter, conf, accumulateDirectories, new PathVisitor() {
> > +      @Override
> > +      public void visit(FileStatus fileStatus) {
>
> oh, it is checked in walkPath
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/kevinweil/elephant-bird/pull/276/files#r2271629>.
>
>
Можешь написать это без eval?
The result at the end is the same
Move up after the `else`.
One newline should do, further down too.
Could `windowID` by dynamic, so the correct headers would be sent when it was a private tab / window?
Нельзя менять входные параметры для дуги, т.к. если ты придумал, что у нас дуга должна задаваться тремя точками, это ещё не значит, что она в таком виде лежит в xml. Я думаю, что в ShapeEditor'e с этим все норм, так что сделай как у них  через 2 угла.
I have removed it, now is as good time as any.
We usually like to `assert()` on things that shouldn't happen, because they invariably do happen :)
Yup, I'll fix this.
LOVE these refactors - much better, thanks!
Blizz used Bolsas.
Agree too, this is what is working quite well in the atmos and optics dox too.
Agree with Mike, and like the optional paramter option (perhaps a `uniform_deviate=None` keyword that only gets queried if using randoms.  I'd make the same comment about the  random number used to pick out a galaxy from the catalogue in the `RealGalaxy` class...
额 。。。。。
+1 for customization -- thanks
Note that this will blow away any content-type or other metadata that was set previously.
Worth adding a "TODO" at the start of this comment.
c'est vraiment pas les memes lois, tu peux difficilement les comparer
It is `cocoa.id`.
I guess it's simpler and more portable to add a MANIFEST.in file with 

include README.rst
recursive-include vaurien *.txt
recursive-include docs *.*
All 4 lines (floating, fixed, parentElement, showAlways) aren't needed anymore due to changes in hallo. Not sure which of them is to have the toolbar in the header though, floating is a good guess.
Awesome. I just implemented a simplified version of this for binary file detection in diff, but we can convert to use this instead.
Why on earth were we... ಠ_ಠ
As per our discussion:

```python
def __eq__(self, another):
    if isinstance(another, TransformRule):
         return self.__dict__ == another.__dict__
    return False
```
this is the same change that inadvertently appeared in my pull request.  It likely shouldn't be here either.
since you extend OBcontroller, you get it's user method.  Application.user() can become just user().
Must extend OBController
Right, all I'm saying is if a node identifies itself as pre-209, instead of simply disconnecting, treat it as if it's version 209. That way if there are nodes that in fact support the newer protocol, but identify themselves as pre-209, they will still work.  If they don't support the newer protocol, the messages won't work anyway and nothing is lost.  Cases where this could potentially happen-- patched pre-209 reference clients, alternative clients, clients that mis-identify themselves in terms of version.  It just strikes me as being more fault-tolerant than disconnecting right away.

That said, it's probably not a huge deal.  Just thought I'd bring it up for consideration.
You misunderstood what ths code does.
it draws 'all non-destroyed limbs'
Can you move these two lines into one line, for ease of searching?
Path-ul trebuie luat din <code>Config::output_schemas</code>. Din ce am inteles eu, nu trebuie luat direct fisierul ci cautat prin toate schemele din folderul cu schemele de output si vazut care corespunde pentru ce avem nevoie. Nu sunt sigur de ultima parte - cred ca cel mai bine ar fi sa intrebam pe forum.
<code>int i;</code>
<code>int top = -1;</code>
<code>int bottom;</code>
<code>int right;</code>
<code>int left;</code>
in loc de
<code>int i, top = -1, bottom, right, left;</code>
Does it make sense to have "Copyright (C) 2012" suffix? The LicenseTemplate doesn't have that. As previously noted im picky about that and would like to have it as homogenous as possible.
yep, a typo... "provided". I'll change it.
Yes, probably, but I think the comment by @fatbusinessman is still valid for this story.
Ich hab da nix geändert ....
Почему нужно закрыть в try..finally? Там же уже функция, которая закроет try..finally, - нужно засовывать еще поверх этого блок?
Здесь надо cast делать
И как прикажешь создавать экземпляр этого класса?
If we had used a hash, this would look like

```ruby
@points[label]
```
that would probably belong to other unit test, the goal of this test is to ensure the specified container has been successfully deleted.
Could the building instructions be merged with the duplicated instructions found elsewhere?
Are you perhaps looking for [Model.objects.get_or_create](https://docs.djangoproject.com/en/dev/ref/models/querysets/#get-or-create)?
I have no idea ;)
Agreed. I've removed lines 168-169.
I would simply use objects rather than classes. The factory would than become the __init__ of a class.
Please add a comment to tell so.
Please do not use mixedCase but only lower_case for variable and method names.
strpos would be faster as it does not need the additional substr operation and memory allocation.
What about checking if `xdebug` extension is loaded before invoking a potentially non-existant functions. Extensions can be checked by using `Runtime::extensionAvailable()` function.
Looks like they were actually tabs.  I tried to tell my editor never to insert tabs, but it looks like it didn't listen... :-/  Fixed now.
rename to multi_testsuite.py

Note the e in suite.
Use const_iterator here
Delete this unused view!
Signature is an unused variable.
Also here, wouldn't enforce any prefix.
This is potentially problematic.  It means a subsequent entries in the hash table may fail to be matched (see code in SuperHashTable::doDeleteElement).  That means you may end up with duplicate entries in your hash table.  Although they will be deduped later (I hope) it is unfortunate.
spilling an entire bucket, stored in its own  hash table would avoid that problem.
wrong indentation (probably using tabs instead of spaces)
It is legal for an XML file to omit the prolog, so here you are relying on Cobertura to continue to emit the prolog.
For me, it creates a symlink `/usr/local/bin/lessc -> /usr/local/lib/node_modules/less/bin/lessc`
Move the `except KeyError:` line up by 1 and inside it replace the `pass` with a `continue`.
せっかくだから、この行コメントはJavaDocコメントにしたら？
Given that the 'DefaultTitle' doesn't contain 'current' we shouldn't add it for the tab title and just use 'TabTitle' as the variable name. I don't see a reason why we should explicitly call it current.
Oh, and update the changelog.
J'en ai également profité pour utilisé le mixin pour le box-shadow http://compass-style.org/reference/compass/css3/box_shadow/
https://github.com/doctrine/dbal/blob/master/lib/Doctrine/DBAL/Cache/ResultCacheStatement.php#L156
@shacker Yeah, I saw that note, I actually think it's important that we define it ourselves.
That way we can:

* get just the amount of data that we want
* make it better for caching
* have a consistent API (e.g. here we're using CamelCase, when decided on snake_case)
* make sure that when we add another feed (e.g. canvas/bspace calendar), we don't have to change a lot.
Or "pyramid_gaussian" in case we wanted to add others (like we named the thresholding funcs).
How much of this is specific to the central body?  Do/should we have a generic function for projecting a bounding sphere into a screen-space rectangle?
As I mentioned today in the SIL meeting, there were accidentally removed by the merging tool. I will put them back.
Don't abuse console.log. We still need to use it to output some information during debugging. My suggestion is use it when you are debugging, and delete it when the debugging is done.
为什么directional light没有设置attenuation？
can you move this line after CGRectContainsPoint(hitRect, point) condition has been met ?
if self.js_changed is true and self.fastdev is false, mine would return false while yours return true.
This can also be undefined, in case of the tab being changed to the 'more' tab, which doesn't exist in the tabs array.
This is not supported by TDOC, unfortunately.  See [Method Parameter Specification](https://wiki.appcelerator.org/display/guides2/TDoc+Specification#TDocSpecification-MethodParameterSpecification)

However, I will move the iOS only note at the end to the first line.
Just checked, both textContent and text are not implemented in android.
Since we added 'state' here, have we checked with iOS to make sure they support it too? If not, we should probably note that in the docs as well.
Good call. I should do something like:

    return (m ? m[0] : name).trim().toLowerCase();
Since the previous line is a return statement, you can get rid of "else" and move the "if" statement onto the next line.
It is easier to redirect URLs which end in '/' here that to figure out a voodoo match for routes files. Simplifies client routes file entires.
Do we really want to pass a logger here?
Just do a getLogger if you need one..
Use same representation for the test readability

```d
formatTest(  ['"':"\"", '\'':"'"],
            `['"':"\"", '\'':"'"]` );
```
It works between various string types. `appender` supports it and its exactly the same constraint that was there before.

I see your point with adding `join(RoR, E)`, but I'd like to separate the refactor from bugfixes/enhancements. If this is accepted then I will pick it up afterwards. There's also a bug with immutable that I want to fix.
> Yes, it is a little tricky, but I added the information here.

Cool, thanks.
Now they get catched, so this hacky code is removed
I've tried to remove "? extends" but it did not work. So I will keep it as it is.
this will have parser order dependencies, maybe this could be a conditional dep on the memcache service?
this line from  LiipImagineBundle Readme IMO she has the right to life
@smurthas is very eager to yes, it's just lower priority as it's more of a cleanup than any functional improvement
well, you are sending the PR to the master branch of the repo. And the master branch of the doc repo is for Symfony master
If you're going to make this method generic, and pull it into the base class, you have to make it _really_ generic, and this line isn't. I'm going to move this into RegistrationEditPatientFragmentController.
spaces round '='
Why the half-second wait? No callback can do this instead?
Would that look nicer?
@body.add_class("#{active_admin_namespace.name}_namespace")
The comment is not often maintained. I like this approach.
range slider submit
@olegz 
I could not understand you, however I've just tested it with Mark's solution and my test passed correctly:
```<property name="@testBean2.name" expression="@testBean"/>```
```<beans:bean id="testBean2" class="org.springframework.integration.config.xml.EnricherParserTests.Target"/>```
and in the end I've gotten **testBean2.name == 'male'**

And off topic: how to make on GitHug commets multi-line code sample?
I left out the prePersist and postPersist methods and calls, as that functionality is already provided by the (http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/events.html)[Doctrine2 event system].
That was from me messing around with things; just forgot to remove it.
I did not know about it, I can do that.
We could prob remove the if check? and do

```python
self.api_section = api_section
# Mandrill divides the api into different sections
for x in ['users', 'messages', 'tags', 'rejects',
              'senders', 'urls', 'templates', 'webhooks']:
    setattr(self, x, MailSnake(apikey, extra_params, api, x))
```

?
全体的に ScalaDoc 書いてもらえますでしょうか。
参考 → http://docs.scala-lang.org/style/scaladoc.html
Cool. So, all I'll do with this PR is update the code to send the current item into the getItemView and then leave it up to the user to override that if they want.
I had tried to use ensureUDFContext() within Loader, but this is only useful if Loader can reliably grab the job Configuration. This isn't always the case when getContextProperties() is called, so I removed use of ensureUDFContext(), but left the definition there.

If you'd like I can create a new pull request which only removes this line.
This test fails on my system.
change to WIDTH_PX
wouldn't *isParameterConstrained* resp. *isReturnValueConstrainted* be nicer?
i like the addition here!
Good catch - I tested this with a Set, so it worked for me :-)
Correct if I'm wrong but I think my implementation is valuable security wise.

If you create an Facebook account you need to verify this account before you can use it. So the Facebook account is sufficiently authenticated. If a user has access to the email address then the account itself is already compromised.
Any reason why you don't pass the test into the callback as a parameter to avoid having to capture it block?
We want to use this tool from our service to generate scripts and this is to make it more reliable.
prob() in examine is a bad idea, it'll reward players who spam the shit out of the verb.
I think when you add offer codes you need to reprice the order based on that. Kinda odd that it does actually update the price even when passing in false
ok then say that. Does that mean one look that works everywhere is responsive? Is doing multiple looks perhaps too much to ask fo someone to do by hand for a job application?
The latter is desired, so I'd say leave that in.  I'd prefer that we take out the former, if we're not going to fail fast with a comprehensive assessment of the field format in the user's query.
rename this to create_filter_matrix and combine motion parameters + derivatives, composite_norm, compcorr components, art outliers

```python
def create_filter_matrix(motion_params, composite_norm, compcorr_components, art_outliers, selector):
    ...
    # ensure all numbers are written to atleast 10 precision digits.
    return filter_file
```

the selector will be a list of booleans corresponding to [motion, motion_deriv, comp_norm, compcorr, art]
for example, selector=[True, False, False, False, False] will only use the motion parameters

this same option should exist for the task preprocessing as well.
pulled this from the api docs...
Didn't know about this trick, nice!
typo, landid === langid

I think this merits a method description. Here's my guess based on what I know:

Returns the language conversion table used to load localized values for certain properties from the locale files.

For each localizable property, such as "title," the proxy should define a second property, such as "titleid", used to specify a 
localization key for that property. If the user specifies a localization key in "titleid", the corresponding localized text from the locale file 
is used for "title."

Subclasses should override this method to return a table mapping localizable properties to the corresponding localization key properties.

For example, if the proxy has two properties, "title" and "text", and the corresponding localization key properties are "titleid" and "textid", this might look like:

   @Override
    protected KrollDict getLangConversionTable()
    {
        KrollDict table = new KrollDict();
        table.put("title", "titleid");
        table.put("text", "textid");
        return table;
    }
`def self.with_puppet` is generally preferable - because you can clearly identify each function individually.
pls add here also javadoc, even though its quite sure what this function does :-)
Please check description of parametres above.
The same, user must run install_sn.php.
It hard to tell from the code what value m_appId may have but I wanted to point out that in the case of public/BIS push m_ppgUrl must have a valid non null non empty string value. In the case of BES/enterprise push the appId can be an empty std::string(""). In either case it cannot be null. It may be necessary, if not handled somewhere else (maybe JSon already handles this), that if m_appId is null that instead an empty string is passed to the constructor call.
Moreso, we add listeners on every show that are never dismissed, doesn't this mean that all of the old callbacks will be invoked forever. And even if we switch to once, there will always be a dangling listener since only callback or dismiss will be called.

I could be wrong, but it feels like this can cause old callbacks to be fired erroneously
As I said, personally I'd rather get the error as a developer and have some hopes of figuring out what went wrong vs returning undefined, but if other people disagree I'm OK with it.
Got rid of the extra tests
the exception puts it back on the queue and another worker will re-try later so why try here?
Täälläkin vois käyttää aikasemmin toteutettua `divides?`-funktiota
You don't need this here. the function statement `function WebView()...` below will be [hoisted up](http://www.adequatelygood.com/2010/2/JavaScript-Scoping-and-Hoisting).