Elliott Sprehn 30c38af903 module.exports should default to an empty object.
Per the spec in modules.md the exports property should default to an
empty object. We lazy allocate it so that modules that just replace it
don't create the empty object and then throw it away.

R=abarth@chromium.org

Review URL: https://codereview.chromium.org/872043003
2015-01-26 11:38:04 -08:00

43 lines
1.0 KiB
C++

// Copyright 2014 The Chromium Authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.
#include "sky/engine/config.h"
#include "sky/engine/core/app/Module.h"
#include "gen/sky/core/EventTargetNames.h"
#include "sky/engine/core/app/Application.h"
namespace blink {
Module::Module(ExecutionContext* context,
Application* application,
PassRefPtr<Document> document,
const String& url)
: AbstractModule(context, document, url),
application_(application) {
}
Module::~Module() {
}
const AtomicString& Module::interfaceName() const {
return EventTargetNames::Module;
}
Application* Module::GetApplication() {
return application();
}
void Module::setExports(ScriptState*, const ScriptValue& exports) {
exports_ = exports;
}
const ScriptValue& Module::exports(ScriptState* scriptState) const {
if (exports_.isEmpty())
exports_ = ScriptValue::createEmptyObject(scriptState);
return exports_;
}
} // namespace blink