------art_10676_668051.1153689412458
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

yadda operators are not supposed to stay till production.

I don't know what's the exact intended use. I don't think there is. I'll
tell you how /I/ would use it (at least how I envision myself using it):

yadda is for when you want to leave a piece of code for later.

You can write a loop or if clause and it won't act differently because of
emtypness. Also, when (if) you get there you'll know why stuff doesn't
behave right - because you didn't implement it yet.

That's why '...' is in my opinion such good syntax for it (but in Ruby would
require to change the parsing yadda yadda yadda).

Another nice thing is that when you are preparing code for release you can
easily *grep yadda *(or *fgrep ...*) and make sure that nothing is left
over.

Simple raise won't do *that* for me.

Side note: I'm not a Seinfeld fan. I've in fact almost never watched it, and
did not watch the yadda-yadda-yadda episode (was it an episode?).

I only refer to it this way because perl does and it makes sense to me.

It would also never get used for other things in my source so the search
won't give false positives.

The implementation isn't perfect - something that gives more info would be
even better - but it's so simple...

It's something so basic and useful that I really don't think it deserves
it's own *require*.

If no one else does, then I guess I'll have to stick it in a header.

I hope other people will too benefit from the idea (call me an idiot but up
to now I had inconsistent behaviour on cases where this would be used -
raise or do nothing or print a random useless flow of information regarding
execution).

And you could change it to:

def yadda(*comment)
   raise "Yadda point reached. Comment: " + comment.shift.to_str
end

Aur.

------art_10676_668051.1153689412458--