global

How can I use global DB variable inside class? Let's say I have this in my config.php $dbh = new PDO("mysql:host=localhost;dbname=mydb", "root", ""); and I want to use this $dbh inside class as follows (MyClass.php) class MyClass { public function DoSomething($plogin_id) { $sql = "SELECT * FROM mytable WHERE login_id = :login_id"; $stmt = $dbh->prepare($sql); //line 14 $stmt->bindParam(':login_id', $plogin_id, PDO::PARAM_STR); } } And inside my index.php file I am using this MyClass as follows: include "config.php"; $MyObject = new MyClass(); $login_result = $MyObject->DoSomething("admin"); It

So I want to trigger an event (pausing/unpausing some media) whenever the user presses spacebar anywhere in the my Swing app. Since there are so many controls and panels that could have focus, its not really possible to add keyevents to them all(not to mention gross). So I found KeyboardFocusManager.getCurrentKeyboardFocusManager().addKeyEventDispatcher() which is awesome, you can register global keypress pre-handlers. There's a major problem though - spaces will be typed all the time in input fields, table cells, etc, and I obviously dont want to trigger the pause event then! So any ideas?

I'm creating a global Facebook object (from android-facebook-sdk) to be able to share it across my activities: public class GlobalVars extends Application { public static final String APP_ID = "123456789"; public Facebook facebook = new Facebook(APP_ID); } In one of the activities I add the LoginButton, as shown in the examples: public class FacebookActivity extends Activity { private LoginButton mLoginButton; private Facebook mFacebook; private AsyncFacebookRunner mAsyncRunner; @Override public void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); mFacebook = (

I am writing an agnostic logging mechanism that works inside the browser and in nodejs (e.g. console.debug is missing in nodejs). // UMD with no dependencies (function(global, factory) { if (typeof module === 'object') { module.exports = factory(); // GLOBAL IS NOT WHAT I WOULD EXPECT, YOU? global.console = factory(); } else if (typeof define === 'function' && define.amd) { define(factory); } else { global.console = factory(); } })(this, function() { function logger() {}; return logger; }); I stumbled upon 2 differences I cannot explain: As expected, for the browser case the variable 'global'

I have a shared resource with high initialisation cost and thus I want to access it across the system (it's used for some instrumentation basically, so has to be light weight). So I created a module managing the setup and access to it. It does a lazy initialise of the resource and stores it in a module global variable. I then use functions of this module across the system to operate on the resource. - Now I am wondering whether (or how often) I will have to reinitialise the resource? - I know objects are garbage collected in CPython on (or better around) zero reference count, but is storing in

I'm making an auto clicker that uses jna to hook global input from the keyboard and mouse. For the keyboard hook im using http://code.google.com/p/goldriver/source/browse/trunk/king/src/jnacontrib/w32keyhook/KeyHook.java?r=36 . I was wondering if there was any possible way to consume the key event so other applications don't process it? Fixed with return new LRESULT (1); Now I'm having a problem with it not continuing with the rest of the code, here is the source. My program keeps listening for keyboard input and doesn't continue to even show the GUI. public class GUI extends javax.swing

I've been reading this book "Javascript Enlightenment" by Cody Lindley. On page 82 he states: "Being explicit (e.g. window.alert() v.s. alert()) costs a little bit more with regards to performance. It's faster if you rely on the scope chain alone and avoid explicitly referencing the head object even if you know the property you want is contained in the global scope." I am kind of curious why this is. I would think that it would be the opposite, because the Javascript interpreter could just skip checking the scope and find it directly. I just don't see how it is beneficial to not specify the

Current situation: I have the current version of my MVC Framework which uses classes as controllers. I have some "vintage" modules from my old MVC Framework which uses simple, flat includes as controllers. Much simplified that means: New Version: <?PHP class blaController extends baseController { private $intVar; function dosomethingFunction() { $this->intVar = 123; $this->view('myView'); } } ?> Old Version: <?PHP $globalVar = 123; // view "controllername" is automatically shown ?> I'm now trying to write a wrapper to be able to use my old controllers in my new MVC without having to rewrite