B
ben
has anyone got or read this book: robert sedgewick "algorithms in c
parts 1-4"?
i'm having an absolute nightmare with the book. amoung other things i'm
trying to construct the necessary support files needed to make use of
the example programmes. (support files as in .h .c files that are
#included and used to compile with).
the programmes are designed to use abstract data types so that you can
drop in different versions of the support files and the main programme
will work happily with the various types (support files that handle
types int, double, variable length strings etc.)
the different implementations and headers of the different support file
types are fragmented throughout the text (sometimes not even code, but
just an english description) and are also incomplete -- some bits that
are required by a program's code don't even have english descriptions
so far as i can tell. so far i've been unable to find a complete set of
any of the support files for any of the types -- some of the parts of
the support files are just assumed and the reader is expected to do
kind of detective work to construct the necessary codewhich is
*completey* crap imo -- it should be on a plate but it's not. i'm
getting severely frustrated because the algorithm side of the book
looks good but i can't get past this basic sort of packaging/logistics
part. (why on earth isn't it made completely obvious? anyway, it
isn't.)
if anyone's followed that book and still have some/any of the code
around, could you post it please? it'd be really appreciated. (a full
set of support files for any one of the types (int, double, variable
length string) would be fantastic. i'm talking about Item.h and ST.h
and also probably Item.c and whatever else if there's more, applicable
in particular to the search section -- chapter 12 onwards).
if not i'm going to post what mess i have so far. now there's threat
you don't want me to follow through on.
the book's code on sedgewick's website is of no use (only to save you
typing) -- it's an exact copy of the code in the book, and is in fact
worse, as there are no indications what so ever of names/labels for the
modules of code.
thanks again, ben.
parts 1-4"?
i'm having an absolute nightmare with the book. amoung other things i'm
trying to construct the necessary support files needed to make use of
the example programmes. (support files as in .h .c files that are
#included and used to compile with).
the programmes are designed to use abstract data types so that you can
drop in different versions of the support files and the main programme
will work happily with the various types (support files that handle
types int, double, variable length strings etc.)
the different implementations and headers of the different support file
types are fragmented throughout the text (sometimes not even code, but
just an english description) and are also incomplete -- some bits that
are required by a program's code don't even have english descriptions
so far as i can tell. so far i've been unable to find a complete set of
any of the support files for any of the types -- some of the parts of
the support files are just assumed and the reader is expected to do
kind of detective work to construct the necessary codewhich is
*completey* crap imo -- it should be on a plate but it's not. i'm
getting severely frustrated because the algorithm side of the book
looks good but i can't get past this basic sort of packaging/logistics
part. (why on earth isn't it made completely obvious? anyway, it
isn't.)
if anyone's followed that book and still have some/any of the code
around, could you post it please? it'd be really appreciated. (a full
set of support files for any one of the types (int, double, variable
length string) would be fantastic. i'm talking about Item.h and ST.h
and also probably Item.c and whatever else if there's more, applicable
in particular to the search section -- chapter 12 onwards).
if not i'm going to post what mess i have so far. now there's threat
you don't want me to follow through on.
the book's code on sedgewick's website is of no use (only to save you
typing) -- it's an exact copy of the code in the book, and is in fact
worse, as there are no indications what so ever of names/labels for the
modules of code.
thanks again, ben.