Write procedural style code that runs asynchronously. It may look synchronous, but it's not!
var Bernhard = ;var models = ;Bernhard;
Under the hood, node-procedural-async uses a combination of Proxies and node-fibers. When you call Bernhard.generate, a proxy class is dynamically generated, instanciated and returned. All calls to the proxy will yield until whatever asynchronous task you started has completed. The asynchronous/synchronous magic comes from fibers, so you must write your procedural-async code inside a function that you pass to Bernhard.async.
Returns an instance that derives from Class. You should return this instance from your asynchronous function immediately.
Call this on the instance you got from Bernhard.generate when your asynchronous function has completed.
Put all your procedural-async code inside a function that you pass to this method. Inside this function, you can try/catch any errors.
Copyright (C) 2013 by Shutterstock Images, LLC
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.