Recognized by Council Add XOR gates

[GaeasSon]

I'm not sure I agree with an odd-parity aggregator when you can create a 4-input odd-parity gate with just 3 XORs or an 8-input with 7. I almost feel bad asking for an XOR block as it is.

Let's go for a more general application block, then. What if we had a multi-input block that extends the definition of the subsequent gate?

• It takes as many inputs as the engine will support.
• It changes an AND to a "true if all" gate.
• It changes an OR to a "true if any"gate.
• It changes an XOR to an "odd parity" gate.
• It changes a NOT to a "true if none" gate. (although that is redundant with (multi->OR->NOT))

In each case the output of a multi-input gate will satisfy both inputs of the AND/OR/XOR gates.

 

[NeonSturm]

You can build a XOR (as in 1 if no or all are 1) with 2 and, 1 or and 1 not

But you can not build an odd-parity for >8 elements with <4 elements.

I'm not sure I agree with an odd-parity aggregator when you can create a 4-input odd-parity gate with just 3 XORs or an 8-input with 7. I almost feel bad asking for an XOR block as it is.

Let's go for a more general application block, then. What if we had a multi-input block that extends the definition of the subsequent gate?

• It takes as many inputs as the engine will support.
• It changes an AND to a "true if all" gate.
• It changes an OR to a "true if any"gate.
• It changes an XOR to an "odd parity" gate.
• It changes a NOT to a "true if none" gate. (although that is redundant with (multi->OR->NOT))

In each case the output of a multi-input gate will satisfy both inputs of the AND/OR/XOR gates.

what about a "false if any"? EDIT: Newbies will always keep asking that! :D

I like your idea of that extender block.
If other logic blocks would have just 2 inputs, it could save memory and speed up processing (a fixed element size rather than a linked list with a object-reference to the next input)

This extender block could hold all inputs and outputs and the logic is applied to each of those.
Do you know how to implement it to also allows flip-flops without more blocks?


I had a similar idea with a block supporting inputs between 2 "logic wall" stoppers for my own code.

 

[GaeasSon]

"False if any" = "true if none"

 

[ltmauve]

The reason having to build XORs out of multiple blocks is annoying is not only do you need like 6 block for one function, it's also limited to two inputs. Single-only isn't useful once you add in a third gate. As I mentioned above, if you want to control something from multiple locations, you need toggablity from every input.(Also, odd-parity is the definition of XOR for electrical engineers. That's what I learned while getting my bachelors, and that's what the software uses.)

 

[NZSmartie]

Sorry for bumping an old post, but I would like to know if this could be "seen" by either the council or by Schine. A block that would help reduce the size of logic designs in game

 

[GaeasSon]

I don't know. Buttons (periodic switches) and flip/flops mostly obviates my need for XOR gates.

 

[Trekkerjoe]

http://starmadedock.net/threads/magnetic-ability-to-rail-docker-xor.20023/

Just putting this here for reference.