You can’t make an omelet…

Cyrus Blather You can t make an omelet | alternative dating

Cyrus Blather You can t make an omelet | alternative dating — Wed, 17 Jun 2009 10:45:42 GMT

PingBack from http://topalternativedating.info/story.php?id=15615

Cyrus Blather You can t make an omelet | work from home

Cyrus Blather You can t make an omelet | work from home — Tue, 16 Jun 2009 16:05:12 GMT

PingBack from http://workfromhomecareer.info/story.php?id=21121

Cyrus Blather You can t make an omelet | Paid Surveys

Cyrus Blather You can t make an omelet | Paid Surveys — Sat, 30 May 2009 01:21:14 GMT

PingBack from http://paidsurveyshub.info/story.php?title=cyrus-blather-you-can-t-make-an-omelet

good to heard

Sasha — Fri, 02 Sep 2005 23:19:58 GMT

Super site!

re: You can’t make an omelet…

Joku — Sat, 22 Jan 2005 22:40:00 GMT

AT,

Perhaps, anyway that is the simplest way to add a note about the issue (atleast until it is fixed, if that is still possible before final) and still making the beta2 deadline.. Unless someone invents something better :)

re: You can’t make an omelet…

AT — Sat, 22 Jan 2005 10:19:00 GMT

Joku,

Actualy - link to documentation will become very annoying after 2 day of usage.
Even more - my "// TODO" comments idea in notImpl sniplet must be changed a little bit to become usefull.

Instead of always writing the same TODO comment - you must set user cursor at location there he can write his own personal comments about reasons why this is not implemented yet.

While this is possible to automaticaly generate some predefined comment - this comments text must be selected to make it possible delete/override with a single keystroke / letter.

Bug triage: 1/20/2005

Shaykatc's WebLog — Sat, 22 Jan 2005 00:31:00 GMT

re: You can’t make an omelet…

Joku — Fri, 21 Jan 2005 22:30:00 GMT

Much simpler fix..

You suggested the "hack" $end$$CallBase$ ..
If there is no time to make the hack properly, consider replacing
$end$$CallBase$

with

// <link to local documentation which explains the different cases of handling the issue>

And one of the cases in the doc would suggest: return base.GetHashCode(); and explain why etc..

And the other docs need also more explaining why things are done like they are, currently one has to go look answers with google. Atleast the local docs could contain links to online commentary forum about the help subject, similar to the great PHP online help!

re: You can’t make an omelet…

Alistair Young — Fri, 21 Jan 2005 14:49:00 GMT

I'd like it put back, and I'd like it with the "return" - but mostly, for my money, I'd like to see the throwing of the exception appear above the base call, just to enforce that I look at *all* those overrides before calling them...

re: You can’t make an omelet…

DrPizza — Fri, 21 Jan 2005 11:46:00 GMT

"BTW, I've discusses this with Cyrus - and proposed to add one more variable $ReturnBase$ thich will be equal to "return $CallBase$" for all return types except "void" one. "

Or you could support void returns so that you can actually do things consistently....