It's UWAweek 48


This forum is provided to promote discussion amongst students enrolled in CITS2002 Systems Programming.
Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.

Displaying selected article
Showing 1 of 919 articles.
Currently 3 other people reading this forum.

 UWA week 40 (2nd semester, week 10) ↓
SVG not supported

Login to reply

3:24am Wed 5th Oct, Christopher M.

> Hello Chris, I'm quite confused with how the trove_file should more or less look like. > How does each file listed in the trove_file store the words to be searched? > - does each of the listed files store those words like a hashtable? > - e.g. file1 - "hello", "hey",... > file2 - "hello", "blah",... > - the given example is where the word "hello" is seemingly stored more than once, but each file stores the word only once > - or should the trove_file be more like storing the listed files, along with a whole list of words found in those files, provided that each word appears only once > > Just to get a clearer picture, I would like you to provide a brief draft of the trove_file structure
I'm not going, or able, to provide a description of the trove-file format, because its design (and implementation) is completely up to you. There is no single required format, else it would have been specified on the project sheet. You will need to design+develop a format that is (obviously) able to store the filenames and the words, and then be able to read it back when searching for a word. There is no requirement to store each filename and each word only once, but having a trove-file that is larger than the total size of all files indexed is undesirable. This is not in the project simply to be annoying - computer users expect searching (of anything) to be quick, and the biggest gains in speed come from reducing the size of data that is read from disk. Moreover, successful completion of this part will improve your understanding of pointers in C.

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  1:17AM Sep 14 2022
Privacy policy