I thought he ment inline conditions as in conditions inside genes.... but thinking about it, it does sound like he means conditions buildt into a single store...
If you want to see examples of Single Store (SS) bots, then look at the SS league... I think OneManBucket is well dokumented, and if you look for the topic in the starting gate containing Brevis then there's a lot of good tips on how to build and debug a SS bot.
If you mean inline conditions, like the ones used inside a gene (Not in the condition space) then they work just like regular conditions, but they won't get and'ed automaticaly.
The way it works is pretty straight forward, if you put something in the boolean stack while inside a gene then it will be a condition for the following lines in the same gene. The boolean used is always the one on top of the stack, so in order to have several conditions you need to and/or them together.
You can also overide any previous conditions by simply adding a new condition without and/or'ing it with the previous ones.
So if you write :
*.eye5 0 =
140 .aimsx store
*.nrg 100 >
40 .up store
Then the 2 conditions are not related, if eye5 is 0 you will turn, if you have over 100 energy you will move forward.
But if you write :
*.eye5 0 =
140 .aimsx store
*.nrg 100 > and
40 .up store
Then you will only move forward when eye5 is 0 and you have over 100 energy. The boolean stack will contain up to 20 booleans I think.
Then there's some additional operator that you can use, not, dupbool and dropbool can be usefull for cutting condition costs :
*.eye5 0 =
*.nrg 100 > and
*.robage 5 < or
140 .aimleft store
dupbool
*.body 50 < and
40 .up store
dropbool
dupbool
*.in1 123 = and
40 .dx store
dropbool
not
40 .aimright store
This will turn left if eye5 is 0 and you have over 100 nrg or if robage is less than 5. It will move forward if body is also less than 50.
If in1 is 123 and the first set of conditions was true then it will also move sideways (But the body size will be irelevant)
This is because the first set was duplicated before the body 50 < part was added, and then the top boolean was dropped, taking us back to the value from the first set of conditions.
In the end if the first set of conditions amounted to false we turn right.
Not sure I'm doing a good job at explaining this... I think theres a section on the wiki about the integer stack and how it works... the boolean stack is pretty much the same just with booleans... in the end it's just a stack (If you've worked with those before) like in any programing laguage... when you write a condition you push the result into the stack, but instead of poping values from it the top value is just used.
You can also read about the boolean operators on the wiki, generaly most of what you need is found on the sysvars and operators page.
(I currently find myself wishing the source was as welldocumented )