Hannie, on Sep 9 2007, 01:51 PM, said:
I played against a pair that played Flannery this summer, they ended up winning the Spingold. So I think we can do without comments like "they must have been confused because they like Flannery".
Also, it seems to me that both meaning of their bid fall under (a) so there is no problem.
A. Well.... Spingold is a
team event, so a
pair couldn't win it...
The Nickell team won the Spingold. Which pair among them plays Flannery? I wasn't aware that any of them do....
And hey, if you can't pick on Flannery, for heaven's sake, what's the fun anyway?
B. The argument that category c is subsumed under a (to some extent anyway) is interesting, and indeed a nice bit of lawyering imo.
This argument is, that the pair is just using a system whereby a 2
♦ opening shows "both majors". Every hand that they open with 2
♦ will necessarily show "both majors" -- either 4-4 or 5-4. So the hands all qualify under a. Item a doesn't specify what the minors are like ..... all that matters is that you hold "both majors."
But ... that is not what 2
♦ shows in their system.
It conveys more information than that. It may be
either
(1) a 5-4 hand in the majors,
or
(2) a hand with 4 (or 5)
♠, 4 (or 5)
♥, 0 or 1
♦, and 4 (or 5)
♣. A 3-suited hand. To hold this hand, you must hold 4
♠, 4
♥ and 4
♣, and your thirteenth card may be any suit.
That is a 3-suited hand. And there is a specific rule addressing 3-suited hands. Yes, of course the hand does contain "both majors." It also contains
♣, by agreement. And there is a special item on 3-suited hands.
So while it is indeed an interesting argument with some merit, I would still hold that their agreement is not simply one that shows "both majors", even though all hands they open 2
♦ will indeed contain "both majors." It is an agreement that specifically promises either a 2-suited (majors) or a 3-suited (majors +
♣) hand.
The intent of the rule, imo, is -- by its language "indicating
one of" as well as by its express consideration of both 2-and-3-suited-hands -- to disallow such systems in the GCC.
But it's an interesting argument with some force. Want to submit it to Mike Flader at ACBL? I wonder if it's been ruled on before.