Sponsored Content
Top Forums Programming Bitwise operation for state machine Post 302880914 by Don Cragun on Tuesday 24th of December 2013 01:44:30 PM
Old 12-24-2013
Quote:
Originally Posted by RudiC
To be on the safe side, you might want to AND the STATE operand with 0xF8 as well, and check that in STATE only one bit is set...
Agreed. I'm just not sure that we have a true specification of what this macro is supposed to do yet. I've worked on a lot of finite state machines, but the state changes described for this project still seem unusual to me. There seems to be a state0, but instead of having a bit identifying state0; it is identified by being not in state1, state2, or state3.

I was expecting to hear that my suggested change is a step in the right direction, but still isn't doing some things right. Should INA_SAVE_APP_STATE(state4) really clear state1, state2, and state3 from appState? Shouldn't there be some way to clear state4 through state8? Shouldn't there be a macro to initialize the state? (Maybe the header always defines appState to be an extern int (or char); but we haven't seen any evidence of that yet, and these macros won't behave as desired if appState is an uninitialized variable allocated on the stack.) There is no defined error mechanism. (What should happen if one calls INA_SAVE_APP_STATE(state1 | state2)?) Et cetera.

I'm still hoping for an actual set of specifications of the allowed state transitions, what happens when an illegal state is passed in, etc.
 

2 More Discussions You Might Find Interesting

1. AIX

Open firmware state to running state

Hi Admins, I am having a whole system lpar in open firmware state on HMC. How can I bring it to running state ? Let me know. Thanks. (2 Replies)
Discussion started by: snchaudhari2
2 Replies

2. Shell Programming and Scripting

Vim function to generate RTL Code(finite state machine) in verilog

Hi I wanted to call the AutoFsm function (given below) in vim to generate a code something like: **********verilog code to generate ************* always @(posedge clk or negedge rst_n) begin if(!rst_n) begin state_r <= #1 next_stateascii_r; ... (0 Replies)
Discussion started by: dll_fpga
0 Replies
XMLRPC::Lite(3) 					User Contributed Perl Documentation					   XMLRPC::Lite(3)

NAME
XMLRPC::Lite - client and server implementation of XML-RPC protocol SYNOPSIS
Client use XMLRPC::Lite; print XMLRPC::Lite -> proxy('http://betty.userland.com/RPC2') -> call('examples.getStateStruct', {state1 => 12, state2 => 28}) -> result; CGI server use XMLRPC::Transport::HTTP; my $server = XMLRPC::Transport::HTTP::CGI -> dispatch_to('methodName') -> handle ; Daemon server use XMLRPC::Transport::HTTP; my $daemon = XMLRPC::Transport::HTTP::Daemon -> new (LocalPort => 80) -> dispatch_to('methodName') ; print "Contact to XMLRPC server at ", $daemon->url, " "; $daemon->handle; DESCRIPTION
XMLRPC::Lite is a Perl modules which provides a simple nterface to the XML-RPC protocol both on client and server side. Based on SOAP::Lite module, it gives you access to all features and transports available in that module. See t/26-xmlrpc.t for client examples and examples/XMLRPC/* for server implementations. DEPENDENCIES
SOAP::Lite SEE ALSO
SOAP::Lite CREDITS
The XML-RPC standard is Copyright (c) 1998-2001, UserLand Software, Inc. See <http://www.xmlrpc.com> for more information about the XML- RPC specification. COPYRIGHT
Copyright (C) 2000-2001 Paul Kulchenko. All rights reserved. This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. AUTHOR
Paul Kulchenko (paulclinger@yahoo.com) perl v5.12.1 2010-03-17 XMLRPC::Lite(3)
All times are GMT -4. The time now is 11:24 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy