From: jan.de.kruyf@gmail.com
Subject: Re: longest path through a task
Date: Thu, 28 May 2015 07:01:58 -0700 (PDT)
Date: 2015-05-28T07:01:58-07:00 [thread overview]
Message-ID: <6486297c-5ba6-4449-93fe-58002f8e0081@googlegroups.com> (raw)
In-Reply-To: <aa9d235c-db21-46e8-ae50-4284e9cb094c@googlegroups.com>
On Thursday, May 28, 2015 at 2:27:18 PM UTC+2, brbar...@gmail.com wrote:
> There are well-known algorithms for computing schedules. I'd recommend
> Sedgewick, R. and Wayne, K., 2011: Algorithms, Fourth Edition, Addison-
> Wesley, Upper Saddle River, NJ. What you want should emerge from a Critical
Shucks, caught sleeping at the wheel again! Yes of course thank you Bruce.
It will probably work much better, together with the execution time measuring device I concocted, then any package.
By the way for whoever comes after me:
ftp://91.193.236.10/pub/docs/linux-support/computer%20science/data%20Structures%20&%20algorithms/%5BPearson%5D%20-%20Algorithms,%204th%20ed.%20-%20%5BSedgewick,%20Wayne%5D.pdf
I was very grateful for it, since to get books here in SA is a major undertaking! The national airline does not transport post anymore for the national post-office because they forgot to pay!.
cheers,
j.
next prev parent reply other threads:[~2015-05-28 14:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 19:38 longest path through a task jan.de.kruyf
2015-05-27 20:09 ` Niklas Holsti
2015-05-28 6:54 ` jan.de.kruyf
2015-05-28 9:04 ` Niklas Holsti
2015-05-28 12:27 ` brbarkstrom
2015-05-28 14:01 ` jan.de.kruyf [this message]
2015-05-28 13:04 ` jan.de.kruyf
2015-05-29 4:38 ` Niklas Holsti
2015-05-28 16:37 ` Simon Wright
2015-05-28 17:43 ` jan.de.kruyf
2015-05-28 17:52 ` Simon Wright
2015-05-28 18:12 ` jan.de.kruyf
2015-05-29 16:31 ` Simon Wright
2015-05-30 10:50 ` jan.de.kruyf
2015-06-01 13:32 ` Patrick Noffke
2015-06-01 19:09 ` Simon Wright
2015-06-02 22:15 ` Stephen Leake
2015-06-01 4:27 ` Windows Text_IO.Get_Line issue tornenvi
2015-06-01 5:01 ` tornenvi
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox