On Wed, 2010-11-10 at 11:34 -0500, Mark Wendt wrote:
... snip
> > (AFAIK :) )
> > - Steve
>
> Steve,
>
> Yes, you're "absolute"ly right... ;-)
>
> Mark
Sorry for rattling the cage.
What I am trying to do is learn enough C to be able to evaluate what the
code is trying to do. Also, to clarify, I added everything after all of
the //'s, therefore they carry no weight.
For the issue of whether operator precedence trumps short circuit, I
suppose that is up to what gcc was programed to do, so I could reference
gcc. Or, I could just write some code to test the different scenarios.
But... if
" if(new_in && new_in != last_in) {"
tests for an edge in the the proper direction, why does the previous
line normalize the edge?
" if(in_edge) new_in = ! new_in;"
or did I get this wrong too?
Somehow I got the impression that comp needed to have all variables
declared in the top portion of the file, and that comp stripped off the
top and placed the variables as needed. I also found that "comp
--compile foobar" creates a file "foobar.c" which might provide some
insight into this. It's like I see what might be a trunk, but I am not
seeing the elephant. I just need to be patient and look for it.
--
Kirk Wallace
http://www.wallacecompany.com/machine_shop/
http://www.wallacecompany.com/E45/index.html
California, USA
------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a
Billion" shares his insights and actions to help propel your
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
