DOCSLIB.ORG

Structures in C Accessing Components of a Structure

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Structures in C Accessing Components of a Structure Structures in C • In C, we can create our own, complex data types. • This is very convenient for modeling real-life objects by CS 201 defining our own data types that represent structured Structure & Union collections of data pertaining to particular objects. • int, double, char are types of variables defined in C. by using structures, you can create your own types – a nice way to extend your programming languages. Debzani Deb • Unlike array, a structure can have individual components that contain data of different types. • Each of these data items is stored in a separate component of the structure and can be referred by using the component name. 1 2 Defining structure using struct Defining structure using typedef # include <stdio.h> • typedef allows us to associate a name with a struct line { Structure line has 4 Components of type int structure. (where else we saw typedef ?) int x1, y1; // Coordinates of one endpoint of a line typedef struct { int x2, y2; // Coordinates of other endpoint of a line int x1, y1; // Coordinates of one endpoint of a line }; int x2, y2; // Coordinates of other endpoint of a line } line_t; int main() { This defines the variable line1 to be a variable of type line int main() { struct line line1; line1 is now a variable of type line_t. line_t line1; } } • Variables may also be declared in the structure definition. • The typedef statement itself allocates no memory. struct line { • A variable declaration is required to allocate storage int x1, y1, x2, y2; space for a structured data object. } line1, line2; 3 4 Accessing components of a structure Assigning values to the components of a structure (from text) • To access a component of a structure, we can use the direct component selection operator, which is a dot/period. typedef struct { int main() { char name[10]; line_t line1; double diameter; line1.x1 = 3; int moons; line1.y1 = 5; double orbit_time, if(line1.y2 == 3) { retation_time; printf(“Y co-ord of end is 3\n”); } planet_t; } } • Direct component selection operator has the highest precedence. See table 11.1 in the text for the operator precedence. 5 6 1 Using Structures Structures as Input parameter • Structures can contain any C type, including arrays, • We can pass structure as input argument to a function. pointers or even other structures as components. • We have to make sure that the function prototype is introduced to compiler after the structure is declared. • Initialization of structures: (similar to arrays) line_t line1 = {3, 5, 6, 7}; typedef struct { char name[10]; • Assignment of entire structures: double diameter; line2 = line1; // assign to each component of line2 a value of int moons; // the corresponding component of line1. double orbit_time, retation_time; Although C permits copying of entire structure, the equality } planet_t; and inequality operator can not be applied to a structured type as a unit. void print_planet (planet_t p1); if (line1 == line2) // Invalid int main() { Also you can’t use structures as argument to printf and … current_planet is passed as input scanf statement. print_planet(current_planet); argument and all the component values … of current_planet are copied to } corresponding formal parameter p1 7 in function print_planet. 8 Structure as output parameter Figure 11.5 Data Areas of main and scan_planet • Structures may contain large amount of data. during Execution of status = scan_planet • If a function needs to modify the content of a structure (&current_planet); Use pointers to pass address of the structure to functions instead of passing the structure by value. Example, status = scan_planet(&current_planet); // Statement in function main 9 10 Few notes about structure Structure as return type of a function • Simple structure declaration • So far, we have seen that the structures are treated mostly like C’s Syntax: structName varName; Example, planet_p p1; simple data types (int, char etc.). One exception though (Anybody?) • A pointer to a structure • Comparatively, C’s processing of array differs a lot from its handling Syntax: structName * ptrName; Example: planet_p * p1_ptr; of simple data types. For example, array can’t be returned as a • Accessing a component of a structure function result. Syntax: varName.componentname; Example: p1.name • However, we can return structure as the function result. Returning a structure from a function means returning the values of all • Accessing a component of a pointer to a structure components. Syntax: (*ptrName).componentname; Example: (*p1_ptr).name /* The brackets are important cause “.” has higher priority than “*” */ • Indirect component selection operator C provides a single operator that combines the function of the indirection (pointer dereference) and component selection operator. For a pointer to a structure, a component can be accessed by using indirection operator “->” Syntax: ptrName -> componentName; Example: p1_ptr -> name; 11 12 2 Structures as components of structures (1) Structures as components of structures (2) • Send structure emp1 as input • Passing a pointer to a structure Structures can contain other structures as members. argument, modify it and then is more efficient. Example: Employee data base return the modified structure to the calling routine. update2 (&emp1); // in main … typedef struct { Member structures must be e = update1(emp1); // in main void update2 (emp_data_t *p) char dept_name[25]; defined beforehand, since the … { int dept_no; compiler must know their size. emp_data_t update1(emp_data_t emp) printf(“Enter department number: “); } department_t; { printf(“Enter department number: “); scanf(“%d”, &n); typedef struct { scanf(“%d”, &n); p ->dept.dept_no = n; emp.dept.dept_no = n; … char name[25]; The size of a pointer to a structure … } int employee_id; is just the size of the memory return emp; • Use -> instead of . to access department_t dept; address and therefore is known. } components of the structure, address_t * add_ptr; So struct address_t can be defined because p is a pointer to a Later. • Involves lots of copying of double salary; structure components to and structure. } emp_data_t; from the function. 13 14 Array of Structures Self-referencing Structures • Structures may contain pointers to variables of their own type typedef struct { (recursive declaration). int id; struct list { int data; double gpa; struct list *next; } student_t; } a, b, c, d; • This may look initially strange, but in real life it is a very very student_t stulist[50]; useful construction. • By using self-referencing structures, variables of that structure type may be linked as follows Accessing array elements a b c d data data data data for (i = 0; i < 50; i++) *next *next *next *next printf (“%d\n”, stulist[i].id); 15 16 Union (1) Union (2) • C provides a data structure called union to deal with • Union provides a space in memory that can be interpreted in situations in which a data object can be interpreted an multiple ways. a variety of ways. union i_or_c { int i; • Like structure, union is a derived data type. On the char ch[4]; other hand, union allows its components to share the } n1, n2; same storage. • You can access n1 and n2 as either as an int or a char[]. •Example n1.i = 10; n2.ch[1] = ‘g’; typedef union { • Memory of a union is allocated according to the largest int i; interpretation. max(sizeof(int), 4*sizeof(char)) float f; } int_or_float; • Union can help you save space in memory – allocate one space in memory and use it in multiple ways. int_or_float a, b, c, d; 17 18 3 Union (3) Two interpretation of parameter hair • Unions are useful only if it is possible to determine within the program which interpretation is currently the valid interpretation. • Unions are mostly used as component of a larger structure, and the larger structure typically contains another component that determines which interpretation of the union is correct at the present time. typedef union { Two interpretations of union h int wear_wig; char color[10]; 0 ? ? ? ? ? ? ? ? ? h.wear_wig } hair_t; r e d d i s h \0 ? ? h.color typedef struct { int bald; hair_t h; } hair_info_t; Referencing the appropriate union component is programmer’s responsibility. 19 20 struct Summary union Summary • struct is a simple tool – combines simpler •Pros types into one larger type. Very tight memory allocation • Powerful for all sort of uses – used throughout Kind of polymorphism for types C programs and operating systems. Useful for maintaining memory that can be interpreted in • It makes modeling the real-life scenario easier. multiple ways • FILE * is a typedef’d struct, but you can use it • Cons without knowing what’s inside it. You have to be careful with interpretation since types are very different at lower level. • You can extend the language by defining your Can make code very confusing if used without enough own types. documentation or improperly. 21 22 structs with union structs with union(cont.) • The program in the next three slides creates a union status { struct personal { union status and makes it a component of int rank; long id; struct personal which is, in turn becomes a char deg[4]; float gpa; component of struct identity. } ; union status level; • The union uses the same storage space for } ; either component rank (int) or deg (char struct identity { char name[30]; string) depending on the answer to the user struct personal student; prompt for student status in function main. } ; 23 24 4 structs with union (cont.) structs with union (cont.) int main() { else { struct identity jb = {“Joe Brown”}, *ptr = &jb; printf (“Enter degree sought – ms or phd\n”); char u_g; scanf (“%s”, &jb.student.level.deg); jb.student.id = 123456; printf (“%s is a %s candidate\n”, jb.name, jb.student.gpa = 3.4; jb.student.level.deg); } /* end of else printf (“Enter Student Status – u or g\n”); scanf (“%c”, &u_g); printf (“%s %d %f\n”, jb.name, jb.student.id, jb.student.gpa); if (u_g == ‘u’) { printf (“%s %d %f\n”, ptr->name, printf (“Enter rank – 1, 2, 3, 4 or 5\n”); ptr->student.id, scanf (“%d”, &jb.student.level.rank); ptr->student.gpa); printf (“%s is level %d\n”, jb.name, jb.student.level.rank); return 0; } /* end of if } // end of main 25 26 5.
Load more

Recommended publications
  • Application of TRIE Data Structure and Corresponding Associative Algorithms for Process Optimization in GRID Environment
    Application of TRIE data structure and corresponding associative algorithms for process optimization in GRID environment V. V. Kashanskya, I. L. Kaftannikovb South Ural State University (National Research University), 76, Lenin prospekt, Chelyabinsk, 454080, Russia E-mail: a [email protected], b [email protected] Growing interest around different BOINC powered projects made volunteer GRID model widely used last years, arranging lots of computational resources in different environments. There are many revealed problems of Big Data and horizontally scalable multiuser systems. This paper provides an analysis of TRIE data structure and possibilities of its application in contemporary volunteer GRID networks, including routing (L3 OSI) and spe- cialized key-value storage engine (L7 OSI). The main goal is to show how TRIE mechanisms can influence de- livery process of the corresponding GRID environment resources and services at different layers of networking abstraction. The relevance of the optimization topic is ensured by the fact that with increasing data flow intensi- ty, the latency of the various linear algorithm based subsystems as well increases. This leads to the general ef- fects, such as unacceptably high transmission time and processing instability. Logically paper can be divided into three parts with summary. The first part provides definition of TRIE and asymptotic estimates of corresponding algorithms (searching, deletion, insertion). The second part is devoted to the problem of routing time reduction by applying TRIE data structure. In particular, we analyze Cisco IOS switching services based on Bitwise TRIE and 256 way TRIE data structures. The third part contains general BOINC architecture review and recommenda- tions for highly-loaded projects.
    [Show full text]
  • C Programming: Data Structures and Algorithms
    C Programming: Data Structures and Algorithms An introduction to elementary programming concepts in C Jack Straub, Instructor Version 2.07 DRAFT C Programming: Data Structures and Algorithms, Version 2.07 DRAFT C Programming: Data Structures and Algorithms Version 2.07 DRAFT Copyright © 1996 through 2006 by Jack Straub ii 08/12/08 C Programming: Data Structures and Algorithms, Version 2.07 DRAFT Table of Contents COURSE OVERVIEW ........................................................................................ IX 1. BASICS.................................................................................................... 13 1.1 Objectives ...................................................................................................................................... 13 1.2 Typedef .......................................................................................................................................... 13 1.2.1 Typedef and Portability ............................................................................................................. 13 1.2.2 Typedef and Structures .............................................................................................................. 14 1.2.3 Typedef and Functions .............................................................................................................. 14 1.3 Pointers and Arrays ..................................................................................................................... 16 1.4 Dynamic Memory Allocation .....................................................................................................
    [Show full text]
  • Abstract Data Types
    Chapter 2 Abstract Data Types The second idea at the core of computer science, along with algorithms, is data. In a modern computer, data consists fundamentally of binary bits, but meaningful data is organized into primitive data types such as integer, real, and boolean and into more complex data structures such as arrays and binary trees. These data types and data structures always come along with associated operations that can be done on the data. For example, the 32-bit int data type is defined both by the fact that a value of type int consists of 32 binary bits but also by the fact that two int values can be added, subtracted, multiplied, compared, and so on. An array is defined both by the fact that it is a sequence of data items of the same basic type, but also by the fact that it is possible to directly access each of the positions in the list based on its numerical index. So the idea of a data type includes a specification of the possible values of that type together with the operations that can be performed on those values. An algorithm is an abstract idea, and a program is an implementation of an algorithm. Similarly, it is useful to be able to work with the abstract idea behind a data type or data structure, without getting bogged down in the implementation details. The abstraction in this case is called an \abstract data type." An abstract data type specifies the values of the type, but not how those values are represented as collections of bits, and it specifies operations on those values in terms of their inputs, outputs, and effects rather than as particular algorithms or program code.
    [Show full text]
  • Data Structures, Buffers, and Interprocess Communication
    Data Structures, Buffers, and Interprocess Communication We’ve looked at several examples of interprocess communication involving the transfer of data from one process to another process. We know of three mechanisms that can be used for this transfer: - Files - Shared Memory - Message Passing The act of transferring data involves one process writing or sending a buffer, and another reading or receiving a buffer. Most of you seem to be getting the basic idea of sending and receiving data for IPC… it’s a lot like reading and writing to a file or stdin and stdout. What seems to be a little confusing though is HOW that data gets copied to a buffer for transmission, and HOW data gets copied out of a buffer after transmission. First… let’s look at a piece of data. typedef struct { char ticker[TICKER_SIZE]; double price; } item; . item next; . The data we want to focus on is “next”. “next” is an object of type “item”. “next” occupies memory in the process. What we’d like to do is send “next” from processA to processB via some kind of IPC. IPC Using File Streams If we were going to use good old C++ filestreams as the IPC mechanism, our code would look something like this to write the file: // processA is the sender… ofstream out; out.open(“myipcfile”); item next; strcpy(next.ticker,”ABC”); next.price = 55; out << next.ticker << “ “ << next.price << endl; out.close(); Notice that we didn’t do this: out << next << endl; Why? Because the “<<” operator doesn’t know what to do with an object of type “item”.
    [Show full text]
  • Subtyping Recursive Types
    ACM Transactions on Programming Languages and Systems, 15(4), pp. 575-631, 1993. Subtyping Recursive Types Roberto M. Amadio1 Luca Cardelli CNRS-CRIN, Nancy DEC, Systems Research Center Abstract We investigate the interactions of subtyping and recursive types, in a simply typed λ-calculus. The two fundamental questions here are whether two (recursive) types are in the subtype relation, and whether a term has a type. To address the first question, we relate various definitions of type equivalence and subtyping that are induced by a model, an ordering on infinite trees, an algorithm, and a set of type rules. We show soundness and completeness between the rules, the algorithm, and the tree semantics. We also prove soundness and a restricted form of completeness for the model. To address the second question, we show that to every pair of types in the subtype relation we can associate a term whose denotation is the uniquely determined coercion map between the two types. Moreover, we derive an algorithm that, when given a term with implicit coercions, can infer its least type whenever possible. 1This author's work has been supported in part by Digital Equipment Corporation and in part by the Stanford-CNR Collaboration Project. Page 1 Contents 1. Introduction 1.1 Types 1.2 Subtypes 1.3 Equality of Recursive Types 1.4 Subtyping of Recursive Types 1.5 Algorithm outline 1.6 Formal development 2. A Simply Typed λ-calculus with Recursive Types 2.1 Types 2.2 Terms 2.3 Equations 3. Tree Ordering 3.1 Subtyping Non-recursive Types 3.2 Folding and Unfolding 3.3 Tree Expansion 3.4 Finite Approximations 4.
    [Show full text]
  • 4 Hash Tables and Associative Arrays
    4 FREE Hash Tables and Associative Arrays If you want to get a book from the central library of the University of Karlsruhe, you have to order the book in advance. The library personnel fetch the book from the stacks and deliver it to a room with 100 shelves. You find your book on a shelf numbered with the last two digits of your library card. Why the last digits and not the leading digits? Probably because this distributes the books more evenly among the shelves. The library cards are numbered consecutively as students sign up, and the University of Karlsruhe was founded in 1825. Therefore, the students enrolled at the same time are likely to have the same leading digits in their card number, and only a few shelves would be in use if the leadingCOPY digits were used. The subject of this chapter is the robust and efficient implementation of the above “delivery shelf data structure”. In computer science, this data structure is known as a hash1 table. Hash tables are one implementation of associative arrays, or dictio- naries. The other implementation is the tree data structures which we shall study in Chap. 7. An associative array is an array with a potentially infinite or at least very large index set, out of which only a small number of indices are actually in use. For example, the potential indices may be all strings, and the indices in use may be all identifiers used in a particular C++ program.Or the potential indices may be all ways of placing chess pieces on a chess board, and the indices in use may be the place- ments required in the analysis of a particular game.
    [Show full text]
  • CSE 307: Principles of Programming Languages Classes and Inheritance
    OOP Introduction Type & Subtype Inheritance Overloading and Overriding CSE 307: Principles of Programming Languages Classes and Inheritance R. Sekar 1 / 52 OOP Introduction Type & Subtype Inheritance Overloading and Overriding Topics 1. OOP Introduction 3. Inheritance 2. Type & Subtype 4. Overloading and Overriding 2 / 52 OOP Introduction Type & Subtype Inheritance Overloading and Overriding Section 1 OOP Introduction 3 / 52 OOP Introduction Type & Subtype Inheritance Overloading and Overriding OOP (Object Oriented Programming) So far the languages that we encountered treat data and computation separately. In OOP, the data and computation are combined into an “object”. 4 / 52 OOP Introduction Type & Subtype Inheritance Overloading and Overriding Benefits of OOP more convenient: collects related information together, rather than distributing it. Example: C++ iostream class collects all I/O related operations together into one central place. Contrast with C I/O library, which consists of many distinct functions such as getchar, printf, scanf, sscanf, etc. centralizes and regulates access to data. If there is an error that corrupts object data, we need to look for the error only within its class Contrast with C programs, where access/modification code is distributed throughout the program 5 / 52 OOP Introduction Type & Subtype Inheritance Overloading and Overriding Benefits of OOP (Continued) Promotes reuse. by separating interface from implementation. We can replace the implementation of an object without changing client code. Contrast with C, where the implementation of a data structure such as a linked list is integrated into the client code by permitting extension of new objects via inheritance. Inheritance allows a new class to reuse the features of an existing class.
    [Show full text]
  • Data Structures Using “C”
    DATA STRUCTURES USING “C” DATA STRUCTURES USING “C” LECTURE NOTES Prepared by Dr. Subasish Mohapatra Department of Computer Science and Application College of Engineering and Technology, Bhubaneswar Biju Patnaik University of Technology, Odisha SYLLABUS BE 2106 DATA STRUCTURE (3-0-0) Module – I Introduction to data structures: storage structure for arrays, sparse matrices, Stacks and Queues: representation and application. Linked lists: Single linked lists, linked list representation of stacks and Queues. Operations on polynomials, Double linked list, circular list. Module – II Dynamic storage management-garbage collection and compaction, infix to post fix conversion, postfix expression evaluation. Trees: Tree terminology, Binary tree, Binary search tree, General tree, B+ tree, AVL Tree, Complete Binary Tree representation, Tree traversals, operation on Binary tree-expression Manipulation. Module –III Graphs: Graph terminology, Representation of graphs, path matrix, BFS (breadth first search), DFS (depth first search), topological sorting, Warshall’s algorithm (shortest path algorithm.) Sorting and Searching techniques – Bubble sort, selection sort, Insertion sort, Quick sort, merge sort, Heap sort, Radix sort. Linear and binary search methods, Hashing techniques and hash functions. Text Books: 1. Gilberg and Forouzan: “Data Structure- A Pseudo code approach with C” by Thomson publication 2. “Data structure in C” by Tanenbaum, PHI publication / Pearson publication. 3. Pai: ”Data Structures & Algorithms; Concepts, Techniques & Algorithms
    [Show full text]
  • 1 Abstract Data Types, Cost Specifications, and Data Structures
    Parallel and Sequential Data Structures and Algorithms — Lecture 5 15-210 (Fall 2012) Lecture 5 — Data Abstraction and Sequences I Parallel and Sequential Data Structures and Algorithms, 15-210 (Fall 2012) Lectured by Guy Blelloch — 11 Septermber 2012 Material in this lecture: - Relationship between ADTs, cost specifications and data structures. - The sequence ADT - The scan operation: examples and implementation - Using contraction : an algorithmic technique 1 Abstract Data Types, Cost Specifications, and Data Structures So far in class we have defined several “problems” and discussed algorithms for solving them. The idea is that the problem is an abstract definition of what we want in terms of a function specification, and the algorithms are particular ways to solve/implement the problem. In addition to abstract functions we also often need to define abstractions over data. In such an abstraction we define a set of functions (abstractly) over a common data type. As mentioned in the first lecture, we will refer to the abstractions as abstract data types and their implementations as data structures. An example of an abstract data type, or ADT, you should have seen before is a priority queue. Let’s consider a slight extension where in addition to insert, and deleteMin, we will add a function that joins two priority queues into a single one. For historical reasons, we will call such a join a meld, and the ADT a "meldable priority queue". As with a problem, we like to have a formal definition of the abstract data type. Definition 1.1. Given a totally
    [Show full text]
  • A Metaobject Protocol for Fault-Tolerant CORBA Applications
    A Metaobject Protocol for Fault-Tolerant CORBA Applications Marc-Olivier Killijian*, Jean-Charles Fabre*, Juan-Carlos Ruiz-Garcia*, Shigeru Chiba** *LAAS-CNRS, 7 Avenue du Colonel Roche **Institute of Information Science and 31077 Toulouse cedex, France Electronics, University of Tsukuba, Tennodai, Tsukuba, Ibaraki 305-8573, Japan Abstract The corner stone of a fault-tolerant reflective The use of metalevel architectures for the architecture is the MOP. We thus propose a special implementation of fault-tolerant systems is today very purpose MOP to address the problems of general-purpose appealing. Nevertheless, all such fault-tolerant systems ones. We show that compile-time reflection is a good have used a general-purpose metaobject protocol (MOP) approach for developing a specialized runtime MOP. or are based on restricted reflective features of some The definition and the implementation of an object-oriented language. According to our past appropriate runtime metaobject protocol for implementing experience, we define in this paper a suitable metaobject fault tolerance into CORBA applications is the main protocol, called FT-MOP for building fault-tolerant contribution of the work reported in this paper. This systems. We explain how to realize a specialized runtime MOP, called FT-MOP (Fault Tolerance - MetaObject MOP using compile-time reflection. This MOP is CORBA Protocol), is sufficiently general to be used for other aims compliant: it enables the execution and the state evolution (mobility, adaptability, migration, security). FT-MOP of CORBA objects to be controlled and enables the fault provides a mean to attach dynamically fault tolerance tolerance metalevel to be developed as CORBA software. strategies to CORBA objects as CORBA metaobjects, enabling thus these strategies to be implemented as 1 .
    [Show full text]
  • Tries and String Matching
    Tries and String Matching Where We've Been ● Fundamental Data Structures ● Red/black trees, B-trees, RMQ, etc. ● Isometries ● Red/black trees ≡ 2-3-4 trees, binomial heaps ≡ binary numbers, etc. ● Amortized Analysis ● Aggregate, banker's, and potential methods. Where We're Going ● String Data Structures ● Data structures for storing and manipulating text. ● Randomized Data Structures ● Using randomness as a building block. ● Integer Data Structures ● Breaking the Ω(n log n) sorting barrier. ● Dynamic Connectivity ● Maintaining connectivity in an changing world. String Data Structures Text Processing ● String processing shows up everywhere: ● Computational biology: Manipulating DNA sequences. ● NLP: Storing and organizing huge text databases. ● Computer security: Building antivirus databases. ● Many problems have polynomial-time solutions. ● Goal: Design theoretically and practically efficient algorithms that outperform brute-force approaches. Outline for Today ● Tries ● A fundamental building block in string processing algorithms. ● Aho-Corasick String Matching ● A fast and elegant algorithm for searching large texts for known substrings. Tries Ordered Dictionaries ● Suppose we want to store a set of elements supporting the following operations: ● Insertion of new elements. ● Deletion of old elements. ● Membership queries. ● Successor queries. ● Predecessor queries. ● Min/max queries. ● Can use a standard red/black tree or splay tree to get (worst-case or expected) O(log n) implementations of each. A Catch ● Suppose we want to store a set of strings. ● Comparing two strings of lengths r and s takes time O(min{r, s}). ● Operations on a balanced BST or splay tree now take time O(M log n), where M is the length of the longest string in the tree.
    [Show full text]
  • Space-Efficient Data Structures for String Searching and Retrieval
    Louisiana State University LSU Digital Commons LSU Doctoral Dissertations Graduate School 2014 Space-efficient data structures for string searching and retrieval Sharma Valliyil Thankachan Louisiana State University and Agricultural and Mechanical College, [email protected] Follow this and additional works at: https://digitalcommons.lsu.edu/gradschool_dissertations Part of the Computer Sciences Commons Recommended Citation Valliyil Thankachan, Sharma, "Space-efficient data structures for string searching and retrieval" (2014). LSU Doctoral Dissertations. 2848. https://digitalcommons.lsu.edu/gradschool_dissertations/2848 This Dissertation is brought to you for free and open access by the Graduate School at LSU Digital Commons. It has been accepted for inclusion in LSU Doctoral Dissertations by an authorized graduate school editor of LSU Digital Commons. For more information, please [email protected]. SPACE-EFFICIENT DATA STRUCTURES FOR STRING SEARCHING AND RETRIEVAL A Dissertation Submitted to the Graduate Faculty of the Louisiana State University and Agricultural and Mechanical College in partial fulfillment of the requirements for the degree of Doctor of Philosophy in The Department of Computer Science by Sharma Valliyil Thankachan B.Tech., National Institute of Technology Calicut, 2006 May 2014 Dedicated to the memory of my Grandfather. ii Acknowledgments This thesis would not have been possible without the time and effort of few people, who believed in me, instilled in me the courage to move forward and lent a supportive shoulder in times of uncertainty. I would like to express here how much it all meant to me. First and foremost, I would like to extend my sincerest gratitude to my advisor Dr. Rahul Shah. I would have hardly imagined that a fortuitous encounter in an online puzzle forum with Rahul, would set the stage for a career in theoretical computer science.
    [Show full text]