Thread: Vectors and Classes

I doubt anyone understands what you're getting at.
A vector for each passenger?
"passenger vector details"?

I would create a class to model a passenger: name, age, food preference, and later you could add boarding pass number, etc.

If you did have data specific to seats, like cabin class or near to an emergency exit, then I would create another class to model a seat and the passenger allocated to it, but presently that doesn't appear necessary.

To model the seat allocation, one approach is to use a vector of vectors of passenger or seat smart pointers, the idea being that an empty seat would have a null pointer, and that the number of seats per row sometimes differs (e.g., across cabin classes, or for safety reasons) so a "jagged 2D array" is appropriate, but this also means that you need to be careful when accessing by index to be sure that the seat exists.

Instead of smart pointers, another approach is to have a default constructed passenger or seat object denote an empty seat.

If your scenario model is simplified such that you assume each row has the same number of seats, then it would be better to have a single large vector of passenger or seat objects, then compute the desired index.

Hi laserlight,

Thank you for your help and advice. I have drafted out my basic example and added the code below - it is such a small program i thought it would be easier to add the code and then i can ask a few other questions.

I can take the passengers details (name, age and sex) in main and add to the 'passenger' vector ok, but my problem is pointing this vectors to the 'seats' vector.

I have declared a *Ptr_passanger pointer at the top of the Passenger class, and i am trying to use in the void Plane::BookSeat() method but this does not seem to work. I also tried declaring the *Ptr_passanger pointer in the BookSeat() method and that throws and error. At this point i am a bit lost, i can point an int to an int ok, but an object to an object in this manner i struggle. I have tried something like this but still no luck, seats[1] = *Ptr_passanger.

If you see any obvious bad coding practices please mention as i am trying to learn classes and vetors.

Look forward to your advice.

Thank,

Rocketman46

Code:

#include "stdafx.h"
#include <iostream>
#include <vector>
#include <algorithm>
#include <string>


using namespace std;


//***************************** Passanger Class ******************************************
class Passanger
{
public:
    void Name();
    void Age();
    void Sex();

    vector<string> passanger;
    vector<string> *Ptr_passanger;
    
private:


};


void Passanger::Name()
{
    string name;
    cout << "Enter name: \n";
    cin >> name;
    passanger.push_back(name);


}


void Passanger::Age()
{
    string age;
    cout << "Enter age: \n";
    cin >> age;
    passanger.push_back(age);
}


void Passanger::Sex()
{
    string sex;
    cout << "Enter sex: \n";
    cin >> sex;
    passanger.push_back(sex);
}


//***************************** Plane Class ******************************************
class Plane : public Passanger
{
public:
    Plane();
    void AvailableSeats();
    void BookSeat();
    void CancelSeat();
    void EmptySeats();


    vector<string> seats;


private:
    
};


Plane::Plane()
{
    // just a basic seat layout to get my program working


    seats.push_back("A1"); // 0
    seats.push_back("B1"); // 1
    seats.push_back("C1"); // 2
    seats.push_back("D1"); // 3
    seats.push_back("E1"); // 4
    
}


void Plane::AvailableSeats()
{
    vector<string>::const_iterator iter;


    for (iter = seats.begin(); iter != seats.end(); ++iter)
    {
        cout << *iter;
        cout << "\t";
    }
    cout << endl;
}


void Plane::BookSeat()
{
    string choice;
    Ptr_passanger = &passanger;


    cout << "Book Seat: \n";
    cout << "Available seats please select one: \n\n";
    AvailableSeats();
    cout << "Select seat: \n";
    cin >> choice; // B1 will be selected for example reasons


    // seats[1] = *Ptr_passanger; // trying to point passanger details to seat loation 1 (B1)


}


void Plane::CancelSeat()
{


}


void Plane::EmptySeats()
{


}


//***************************** Main ******************************************
int main()
{
    Plane passanger1;


    cout << "Welcome to Airline Booking\n\n";
    cout << "Please select from the following choices: \n\n";


    int choice;
    
    do
    {
        cout << "\n\n";
        cout << "1) View available seats: \n";
        cout << "2) Make a booking: \n";
        cout << "3) exit: \n\n";
        cin >> choice;


        switch(choice)
        {
            case 1:
            {
                passanger1.AvailableSeats();
                break;
            }


            case 2:
            {
                cout << "Please select a seat: \n\n";
                passanger1.Name();
                passanger1.Age();
                passanger1.Sex();
                passanger1.BookSeat();
                break;
            }


            case 3:
            {
                cout << "exit.\n\n";
                break;
            }


            default:
            {
                cout << "Sorry try again. \n\n ";
                break;
            }


        }


    } while (choice != 3);


    return 0;
}

Surely a plane is not a passenger? A plane has passengers (or it has seats that may be occupied by passengers).

Class diagram - Wikipedia
A plane and it's passengers are a thing that the airline specifies.

A plane could be a cargo plane.
A passenger could decide to take the train instead.

Originally Posted by RocketMan46

So 'Plane' and 'Passenger' classes are now separated, and 'Plane' doesn't inherit from the 'Passenger' class. So my next step is trying to get the 'passenger' vector to point to the 'seats' vector. Due to both of these vectors being public (global) is it better to do this pointer math in 'main' or in the 'Plane' classes. What is the correct OOP way?

The Passenger class should model a single passenger. That is, it should not have a vector of strings named "passanger", and I don't see a reason for Ptr_passanger.

A plane has one or more seats, each of which has zero or one passenger, and you could also say that a plane has zero or more passengers. In post #4, I already suggested a few ways how you might model this. You can come up with a Seat class to model a single seat, or you could directly use the Passenger class; it all depends on exactly what you want to model. If you just want to map seat numbers to Passengers, then you could very well go with a std::map<std::string, std::unique_ptr<Passenger>>, but then you may find it more difficult to do things like identify all the passengers in a row.

The Passenger, Plane, and Seat classes should not have member functions that do interactive I/O. For example, this is wrong:

Code:

void Passanger::Name()
{
    string name;
    cout << "Enter name: \n";
    cin >> name;
    passanger.push_back(name);
}

This kind of code should go in a non-member function that makes use of the interface of the Passenger class.

Not Relevant: Psst, hey, don't follow the OOP hole; it's scary
Super Relevant: ..psst, try this

(0) let's suppose we have a Data Structure named BUFFER

(1) the first container in BUFFER is a

Code:

 vector<uint32_t> _id_

(1.1) _id_ contains all the passengers ids; Attention: All ids are unique, like all people on this earth.. and all ids are natural numbers (e.i 1,2,3,4,..).
(1.2) _id_ is the most trivial and important container in BUFFER
(1.3) every new passenger gets a new id; if for some

Code:

n >= 0, if (_id_[n] <= 0) is true 

then the nth passenger does not exist.
(2.) Every passenger has a known/fixed number of features like the ones you mentioned (they could have more). These features are: age; phone number; ACTUAL id number; flight "something"; "has the passenger arrived yet"; "how many cpu cycles did he skip due to his inability to recognize the presence of a well established dogma" (passive aggressive OOP vs DOD pun); The number of bags he brings; etc. NOTICE that all of these features are addressable via native types (unsigned int, int, bool(C doesn't like these), and more);
(2.1) The next part is to create a container for each feature of type passenger feature type that we want to address.
very Pseudo-code

Code:

BUFFER{
    Vec<uint32> _id_;
    /*containers with the passenger features */
    Vec<uint32> _planeID_;
    Vec<uint8> _numBags_;
    .
    .
}

In a short schema:

Code:

for some n >= 0
_id_[n] : id of nth passenger
_numBags_[n] : number of bags the nth passenger brings
_planeID_[n] : the id of the aircraft the nth passenger was assigned to
, provided that (_id_[n] > 0) is true

You could also have an AIRCRAFT_BUFFER with the same formatting.

I mean, this is one way of Designing your structures of data before you start filling anything with eternal loops of iterators; I like this way a lot. This was the first thing that came out of the top of my head.. hope i could've helped with the designing part. stay safe; stay oop minimal.