[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: How to implement this with LuaMacro?
- From: Pavel Shevaev <pacha.shevaev@...>
- Date: Sat, 23 Jan 2010 10:03:46 +0300
> Asking about using the C API to run 'require' in order to Lua macros
> running from the C side... that's not a very typical combination of
> n00bie topics!
Heh, thanks ;)
> A little off topic, but I'm curious about PARAL and SEQ. Is this an
> interface to a language/model that supports explicitly specifying
> parallel/sequential code?
Well, it's an interface to the simple implementation of an AI behavior
tree. The whole model is written in C++ while Lua is used as a
declaration language for tree composition. PARAL - is a block where
nodes are executed in parallel until one of them completes, SEQ - is a
block where nodes are executed one after each other until one of them
fails. There are a few more core building blocks like for example
selectors, sort of a switch/case construct.
By the way, I'm thinking how to get rid of ADD constructs using
LuaMacro since they are redundant. So instead of:
It could simply be:
> Do you have a link to some context for your AI
> use case? Googling results in a flood of hits.
There is a great site aigamedev.com with LOTS of information on AI and
behavior trees in particular. You can start with this introduction
video http://aigamedev.com/open/articles/behavior-trees-part1/ and
watch rest 2 and 3 parts by changing the last number in the url.
> The information contained in this email transmission may contain proprietary and business
> sensitive information. If you are not the intended recipient, you are hereby notified that
> any review, dissemination, distribution or duplication of this communication is strictly
> prohibited. Unauthorized interception of this e-mail is a violation of law. If you are not
> the intended recipient, please contact the sender by reply email and immediately destroy all
> copies of the original message.
> Any technical data and/or information provided with or in this email may be subject to U.S.
> export controls law. Export, diversion or disclosure contrary to U.S. law is prohibited.
> Such technical data or information is not to be exported from the U.S. or given to any foreign
> person in the U.S. without prior written authorization of Elbit Systems of America and the
> appropriate U.S. Government agency.
Best regards, Pavel