in reply to Re^13: Your main event may be another's side-show. (Coro)
in thread Your main event may be another's side-show.

*sigh* You misunderstand again.

If I misunderstand--and I don't think I do--its because your descriptions (despite their verbosity(*)), are lacking.

But then, we all know the best description of code, is the code itself.

(*)If you left out the attempts at snide put-downs, you'd perhaps make a better fist of your descriptions.

Ps. This is how quick it is to knock up a PoC.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
RIP an inspiration; A true Folk's Guy
  • Comment on Re^14: Your main event may be another's side-show. (Coro)

Replies are listed 'Best First'.
Re^15: Your main event may be another's side-show. (Coro)
by tye (Sage) on Oct 22, 2010 at 04:39 UTC
    Read more... (353 Bytes)

    Thanks for mentioning that, though. It makes some of your reactions easier to understand.

    Read more... (3 kB)
    But then, we all know the best description of code, is the code itself.

    The "code itself" (for any of the cases I'm talking about) is many tens of thousands of lines and so makes for quite a horrid "description", actually. It is nice that you find it extremely easy to make short mock-ups in code that you find adequately convey a complex situation that you are trying to describe. I find quick mock-ups very often end up with the "quick" part being relatively quick but that the "last 10%" (of actually making it work and thus be useful as an example) can take even more than the fabled "90% of the time". So I don't embark on such time sinks for myself much.

    And then there are tons of details in working code that can't be "glossed over" and so figuring out what the point of the mock-up was from reading the code is often not an obvious step for me. So I probably wouldn't understand your discussion in the form of code any better than you understand me. C'est la vie.

    - tye        

[reply]
      And then there are tons of details in working code that can't be "glossed over" and so figuring out what the point of the mock-up was from reading the code is often not an obvious step for me. So I probably wouldn't understand your discussion in the form of code any better than you understand me.

      I'm sorry, but I simply do not believe that you can't demonstrate your magical "coroutines without cede points" in a few lines of code, without the need to post some humongous lump of proprietary code.

      Which just leaves me thinking I know the real reason you'd rather write at length on distractions, than do so.

      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]

In Section Meditations