static-methods

I'd like to do something like this: class SillyWalk(object): @staticmethod def is_silly_enough(walk): return (False, "It's never silly enough") def walk(self, appraisal_method=is_silly_enough): self.do_stuff() (was_good_enough, reason) = appraisal_method(self) if not was_good_enough: self.execute_self_modifying_code(reason) return appraisal_method def do_stuff(self): pass def execute_self_modifying_code(self, problem): from __future__ import deepjuju deepjuju.kiss_booboo_better(self, problem) with the idea being that someone can do >>> silly_walk = SillyWalk() >>> appraise = walk() >>> is_good

I think I need some help understanding how static objects persist in an ASP.Net application. I have this scenario: someFile.cs in a class library: public delegate void CustomFunction(); public static class A { public static CustomFunction Func = null; } someOtherFile.cs in a class library: public class Q { public Q() { if (A.Func != null) { A.Func(); } } } Some ASP.Net page: Page_Init { A.Func = MyFunc; } public void MyFunc() { System.IO.File.AppendAllText( "mydebug.txt", DateTime.Now.ToString("hh/mm/ss.fff", Session.SessionID)); } Page_Load { Q myQ = new Q(); System.Threading.Thread.Sleep

Is it possible to return an object from a static method in C++ like there is in Java? I am doing this: class MyMath { public: static MyObject calcSomething(void); private: }; And I want to do this: int main() { MyObject o = MyMath.calcSomething(); // error happens here } There are only static methods in the MyMath class, so there's no point in instantiating it. But I get this compile error: MyMath.cpp:69: error: expected primary-expression before '.' token What am I doing wrong? Do I have to instantiate MyMath? I would rather not, if it is possible. Use :: instead of . MyObject o = MyMath:

I am wondering do all the local variables become static if we declare them in a static method ? for example: public static void A(){ int x [] = {3,2}; changeX(x); for (int i = 0; i< x.length; i++){ System.out.println(x[i]); // this will print -1 and 1 } } private static void changeX(int[] x){ x[0] = -1; x[1] = 1; } As far as I understand that Java is pass by value always, but why the state of X has changed after we made the changeX call ? Can anyone explain that please ? and can anyone explains how does Java deal with static variables in terms of memory allocation ? and what happen if we pass

C++ syntax allows defining overloaded operators either inside the struct/class like: struct X { void operator+(X); } or outside of the struct/class like: void operator+(X, X); but not as struct X { static void operator+(X, X); } Does any body know reasons for this decision? Why the third form is not allowed? (MSVC gives a syntax error). Maybe there is some story behind this? p.s. Presence of the first and the second definitions at the same time creates ambiguity: 1>CppTest1.cxx 1>c:\ballerup\misc\cf_html\cpptest1.cxx(39) : error C2593: 'operator +' is ambiguous 1> c:\ballerup\misc\cf_html