Cenoman wrote:SpAce wrote:I still don't like your use of the '*' in nested chains (and also subchains with a different meaning). I can't help that it always looks like a memory chain to me.
I am aware. You already complained several times about it!
I know, but this is the first time you responded
Thanks for that. I won't bug you about it after this. (I still wish you'd respond to the
question about fish notation. In both cases I'm perfectly fine if you stick to your old ways, but I'm just interested in your reasons. That's all.)
I dislike memory chain so strongly that I never write one (and quite never read posted ones)
I know. That's why it's obvious that your use of the '*' is not related to memory chains, but it's only obvious to those who've been around long enough to know that. You might remember that I had to ask when I first saw you use it for a nested chain, because the only association I'd seen before was with memory chains. So, I would claim that it's not intuitively understandable.
So, making a chain look like a memory chain is out of my concerns
.
I'd presume just the opposite! If I really dislike something I usually go out of my way to avoid any apparent association that could make someone think otherwise.
Now the "*" symbol is one of the easiest to use (at least on French azerty keyboards).
Understandable.
I consider that writers of memory chains are so minority that I do not agree with leaving them exclusively use the "*" symbol. Let them find another one !
Are they a minority? Of the current or recent regulars I've seen memory chains used at least by myself, Clement, SteveG, and Phil. I'd rather guess that nested chains and their users are probably a rarer variety, as it's a more advanced technique. (And of the nested chain users I think you're the only one here who uses the '*' for that purpose, while all the memory chain writers use it as the primary memory marker without exception. So at least in this context your usage is in the clear minority.)
I tend to avoid memory chains just because they're not very interesting to write, but I have no problem writing or reading them either. Sometimes one is the best option, because it's often the cheapest way to write a simple net. It's straight-forward to write and to understand, and it usually takes up the least amount of effort and space compared to split-nodes, nested chains, net diagrams, and krakens. There's absolutely no difference in functionality or reversibility (if correctly written and interpreted), so why not? Their biggest fault is that they're not valid AICs, but as long as everyone knows that, it's not a practical problem.
(Not sure they were the first users...)
I wouldn't know about that. Either way I think it's more relevant how most people interpret it now.
Anyway, like I said, I'm satisfied with your response. I won't bring this up again!
You propose alternative AICs:
(18)r19c1 = (859*)r934c7 - (9=184)r4c845 - (4|*9=71)r6c58 => -1 r6c1
(18)r19c1 = (85)r93c7 - (8|5)r4c7 = (9,184)r4c7845 - (9|4=71)r6c85 => -1 r6c1
No further comment about the first one !
Well, it's the least elegant for sure, but it's also probably the shortest way to arrive at the conclusion. It's quite simple too, and I would imagine that even a relative beginner could write and read that. So, I don't think it's totally without merit.
Personally I welcome a large variety of logic and notations, as long as they're correct and understandable. There's something to learn from them all, and any artificial restriction denies that opportunity. For example, I thought it was refreshing that Clement used an honest Nishio recently (though I wouldn't want to see it very often).
I would not qualify the second one "classical". To me, nodes with "|"symbols and split nodes as (9,184)r4c7845 are practiced by rather advanced sudoku players.
Of course. Yet I'd put a nested chain even higher up in the food chain. While the notation within the nested chain might be simpler, the overall logic is more complex -- at least from some point of view. It's a bit like recursion vs looping in programming. One is more elegant, the other is usually simpler to understand.
Here one that sticks to both the matrix and the chain. In the light of your comments, I guess it is unambiguous and provides good clarity.
Indeed! Very nice. Krakens are often the most readable variants, but they're not without faults either. They take up space and are the hardest to mark (and read) on the grid because of the discontinuous and complex lettering schemes. The latter especially is one reason why I avoid them, or at least don't always bother with elaborate grid markings with them.
(PS Your post doesn't appear as having been edited. I'd not have answered the first version...
)
I wrote the first version in a hurry, so I rewrote it the way it was supposed to be. The whole point of the original was to show that there was (imho) a relatively simple way to see the logic without nested chains and matrices. It wasn't meant as a criticism against your more elegant way at all, but I realized it could have seemed that way.