|
![](/i/fill.gif) |
Orchid XP v8 wrote:
> function other than how long it's going to take and how much memory it's
> going to eat?
No, you can't tell how long it's going to take or how much memory it'll use.
You can only tell if it's going to take more than X time or more than Y
memory. You do that by running it until it either halts or exceeds that
limit. (And you can tell if you got in a loop using only a fixed amount of
memory, so that's not hit by the halting problem.)
That's different from figuring out the minimum X time to doesn't take longer
than, for example.
--
Darren New, San Diego CA, USA (PST)
"We'd like you to back-port all the changes in 2.0
back to version 1.0."
"We've done that already. We call it 2.0."
Post a reply to this message
|
![](/i/fill.gif) |