in reply to Re^7: Unparseability is A Good Thing
in thread Unparseability is A Good Thing

but what if your prototype leads to a function pointer that gets borked partway through

Sounds like you're talking about bugs, resource problems and other real-world considerations. Those are implementation issues, not algorithmic issues, and determinism is a property of algorithms.

So yes, those are irrelevant. I never said they were.

As for reference material, I often wrongly assume everyone went through comp sci.

I have a B.CS. The course in which this was taught had a very boring teacher. I needed a booster.

Replies are listed 'Best First'.
Re^9: Unparseability is A Good Thing
by Zen (Deacon) on Aug 28, 2009 at 16:44 UTC
    Bugs, yes, but also parseability problems by your definition. If the parser cannot be expected to compute bad programming in the C example due to execution details, how can it be expected to in perl or any language?

    I am convinced all mod comp courses are snoozefests. It's like being taught the identity property in middle school and gritting your teeth at how obvious it all is. Yet the textbook costs over $100- people get paid for this!
[reply]

In Section Meditations