Below are many examples of function hoisting behavior in JavaScript. Ones marked as works successfuly print 'hi!' without errors.
To play around with these examples (recommended) clone them with git and execute them with e.g. node a.js
(I may be using incorrect terms below, please forgive me)
Rich Hickey • 3 years ago
Sorry, I have to disagree with the entire premise here.
A wide variety of experiences might lead to well-roundedness, but not to greatness, nor even goodness. By constantly switching from one thing to another you are always reaching above your comfort zone, yes, but doing so by resetting your skill and knowledge level to zero.
Mastery comes from a combination of at least several of the following:
Before doing anything else, install those:
| package j2p; | |
| import japa.parser.JavaParser; | |
| import japa.parser.ParseException; | |
| import japa.parser.ast.CompilationUnit; | |
| import japa.parser.ast.ImportDeclaration; | |
| import japa.parser.ast.PackageDeclaration; | |
| import japa.parser.ast.body.BodyDeclaration; | |
| import japa.parser.ast.body.ClassOrInterfaceDeclaration; | |
| import japa.parser.ast.body.FieldDeclaration; |
This was posted as an email to python-dev.
Since I signed up for the python-dev mailing list way back in June 2002, there seems to be a cycle where we as a group come to a realization that our current software development process has not kept up with modern practices and could stand for an update. For me this was first shown when we moved from SourceForge to our own infrastructure, then again when we moved from Subversion to Mercurial (I led both of these initiatives, so it's somewhat a tradition/curse I find myself in this position yet again). And so we again find ourselves at the point of realizing that we are not keeping up with current practices and thus need to evaluate how we can improve our situation.
Now it should be realized that we have to sets of users of our development process: contributors and core developers (the latter whom can play both roles). If you take a rough outline of our cur
| - Set default language and all languages to WordPress/Babble | |
| - Loop over all posts and load the translations inside post_content to an array | |
| - Loop the array and skip the default language. | |
| - Babble_Jobs->create_post_jobs( (object) $curren_post, (array) $language_codes ) | |
| - You will get post ids back and need to call the next function. | |
| - Babble_Post_Public->initialise_translation( $original_post, $lang_code ) | |
| - For the behaviour it's best to look at Babble_Jobs->save_job() which is called by the save_post hook | |
| - when successful the default language content should become post_content |
| <?php | |
| define("SHARED_SECRET", "sup3rs3cr3t!!"); | |
| if(!function_exists('hash_equals')) { | |
| function hash_equals($str1, $str2) { | |
| // Run constant-time comparison for PHP < 5.6 which doesn't support hmac_equals | |
| $str1_len = strlen($str1); | |
| $str2_len = strlen($str2); |
| <?php | |
| define("SHARED_SECRET", "sup3rs3cr3t!!"); | |
| function signString($string_to_sign, $shared_secret) { | |
| return hash_hmac("sha512", $string_to_sign, $shared_secret); | |
| } | |
| $payload = array( |