Mon Jun 14, 2004, 08:49am
|
 |
Get away from me, Steve.
|
|
Join Date: Aug 2000
Posts: 15,785
|
|
Quote:
Originally posted by MarionTiger
Quote:
Originally posted by Rich Fronheiser
Quote:
Originally posted by MarionTiger
Quote:
Originally posted by akalsey
At the risk of hijacking this thread, that's the problem with local rules. No one really thinks them through and they are rife with ambiguity and sometimes unintentionally conflict with other rules.
How do you call a person out for throwing a bat? The defense did nothing to earn the out. And how far does the bat have to travel before it is considered thrown? 3 feet? What if someone tosses it 2 feet, 10 inches? Assuming that this rule is to prevent dangerous flying objects, do you award a batter first if the catcher throws his mask?
What if the batter takes ball 4 and then tosses his bat to the dugout? Is he out? What happens to runners on base?
What happens if he hits a home run and when dropping the bat it travels "too far?" Is he out? What about the runners? When does the out occur? At the time the bat is thrown, on appeal, or at the end of the play?
Was any of this considered when creating a rule that you can't throw a bat?
|
I don't disagree with what you are saying, but I think that's why you get one warning. Because it is not a clear rule and is a judgement call. I've never seen this rule get over-enforced.
|
I've never seen this rule actually in place. Frankly, it's stupid. Outs should be earned on the field, not given to teams for no good reason. Warn, then eject is a much better way to handle this kind of a situation.
|
I don't have a problem with that except it would still result in an out then, and everytime that player would be scheduled to appear at the plate in our league.
|
Well, sounds like you're following a stupid local rule with another. Our local league bats everyone. I ejected a 13-year-old the other night. No penalty -- you just skip over the ejected batter.
|