[EMAIL PROTECTED] wrote:
> Basically, I agree that often the local state is much more useful. It
> just seems to me that for some application it's an overkill. Like say,
> for Turtle [1] (no jokes, please :) or PostScript [2].
Sounds also a bit similar to what happens under the hood in Open GL an
On Sat, 15 Dec 2007 01:07:17 -0800, tuom.larsen wrote:
...
> later in the library I would like to expose the
> simplified interface as well:
>
> _machine = StateMachine()
> function0 = _machine.function0
> function1 = _machine.function1
> function2 = _machine.function2
> ...
>
> Is there a way t
On Dec 15, 1:50 am, Steven D'Aprano <[EMAIL PROTECTED]
cybersource.com.au> wrote:
> On Fri, 14 Dec 2007 23:06:28 +0100, Bruno Desthuilliers wrote:
> > Now the question is: why do you think it's so important for your users
> > to only see functions ? What's so wrong with:
>
> > from state_machine im
On Fri, 14 Dec 2007 23:06:28 +0100, Bruno Desthuilliers wrote:
> Now the question is: why do you think it's so important for your users
> to only see functions ? What's so wrong with:
>
> from state_machine import *
> m = get_state_machine()
> m.set_state(42)
I can't speak for the "only" part, b
On Dec 15, 12:02 am, "Chris Mellon" <[EMAIL PROTECTED]> wrote:
> On Dec 14, 2007 4:43 PM, <[EMAIL PROTECTED]> wrote:
>
>
>
> > On Dec 14, 11:06 pm, Bruno Desthuilliers
> > <[EMAIL PROTECTED]> wrote:
> > > [EMAIL PROTECTED] a écrit :
>
> > > > Dear list,
> > > > I'm writing very simple state machin
On Dec 14, 2007 4:43 PM, <[EMAIL PROTECTED]> wrote:
> On Dec 14, 11:06 pm, Bruno Desthuilliers
> <[EMAIL PROTECTED]> wrote:
> > [EMAIL PROTECTED] a écrit :
>
> >
> > > Dear list,
> > > I'm writing very simple state machine library, like this:
> >
> > > _state = None
> >
> > > def set_state(state):
On Dec 14, 11:06 pm, Bruno Desthuilliers
<[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] a écrit :
>
> > Dear list,
> > I'm writing very simple state machine library, like this:
>
> > _state = None
>
> > def set_state(state):
> > global _state
> > _state = state
>
> > def get_state():
> >
[EMAIL PROTECTED] a écrit :
> Dear list,
> I'm writing very simple state machine library, like this:
>
>
>
> _state = None
>
> def set_state(state):
> global _state
> _state = state
>
> def get_state():
> print _surface
>
NameError here !-)
>
> but I hate to use global variable
On Dec 14, 11:52 am, [EMAIL PROTECTED] wrote:
> Dear list,
> I'm writing very simple state machine library, like this:
>
> _state = None
>
> def set_state(state):
> global _state
> _state = state
>
> def get_state():
> print _surface
>
> but I hate to use global variable. So, please, is
On Dec 14, 7:35 pm, Matimus <[EMAIL PROTECTED]> wrote:
> On Dec 14, 8:52 am, [EMAIL PROTECTED] wrote:
>
>
>
> > Dear list,
> > I'm writing very simple state machine library, like this:
>
> > _state = None
>
> > def set_state(state):
> > global _state
> > _state = state
>
> > def get_state()
On Dec 14, 8:52 am, [EMAIL PROTECTED] wrote:
> Dear list,
> I'm writing very simple state machine library, like this:
>
> _state = None
>
> def set_state(state):
> global _state
> _state = state
>
> def get_state():
> print _surface
>
> but I hate to use global variable. So, please, is
On Dec 14, 2007 10:52 AM, <[EMAIL PROTECTED]> wrote:
> Dear list,
> I'm writing very simple state machine library, like this:
>
>
>
> _state = None
>
> def set_state(state):
> global _state
> _state = state
>
> def get_state():
> print _surface
>
>
>
> but I hate to use global variable
Dear list,
I'm writing very simple state machine library, like this:
_state = None
def set_state(state):
global _state
_state = state
def get_state():
print _surface
but I hate to use global variable. So, please, is there a better way
of doing this? All I want is that a user has
13 matches
Mail list logo
