Skip to content

Latest commit

 

History

History
262 lines (221 loc) · 14.1 KB

01GettingStarted.md

File metadata and controls

262 lines (221 loc) · 14.1 KB

Data Structures & C++ for C Coders

Lecture Notes by idebtor@gmail.com

Getting Started

To get started, do the first thing first:

  1. Read README.
  2. Read Syllabus.
  3. Read 'GettingStarted' - this file
  4. Follow instructions in 'GettingStarted' as soon as possible(ASAP).

These reading materials is available at my github.com/idebtor/nowic.

Join Piazza.

There are two ways to join Piazza, go the www.piazza.com.

  • To join Piazza, you may need the following information and

    • School: Handong Global University
    • Course: Data Structures and C++ for C Coders

  • If you have an email address that ends with ~.hgu.edu or ~.handong.edu domain and use it everyday, go the www.piazza.com and follow the instructions in the website.

  • On your request with your email address, I may register it for you. We'll be conducting all class-related discussion here this term. The quicker you begin asking questions on Piazza (rather than via emails), the quicker you'll benefit from the collective knowledge of your classmates and instructors. We encourage you to ask questions when you're struggling to understand a concept—you can even do so anonymously.

Install GCC (GNU Compiler Collection) for Mac OS X

Install GCC (GNU Compiler Collection) for Windows

  • To use g++ in Windows, we need to install two packages:
    • MSYS2
    • MinGW-w64

Install MSYS2 for Windows

Install MinGW-w64 (64 bit version recommended) for Windows

  • For MinGW-w64, follow this good installation guide available.
    • IMPORTANT NOTE During the installation, select the following option:
      Architecture  x86_64
    instead of 
      Architecture  xi686
    • After installation, don't forget the installation path to PATH environment variable. In my case, the installation path was:
    C:\Program Files\mingw-w64\x86_64-8.1.0-posix-seh-rt_v6-rev0\mingw64\bin

Checking GCC installation:

  • Start a console through Mintty if available, otherwise use cmd or PowerShell in Windows.

  • To test installation, run the command g++ --version and see the following:

    $ g++ --version
g++.exe (x86_64-posix-seh-rev0, Built by MinGW-W64 project) 8.1.0
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

    or (if you installed it through MSYS2)

    g++ --version
g++.exe (Rev2, Built by MSYS2 project) 9.2.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

  • If you see something different from x86_64-posix-seh-rev0 or Built by MSYS2 project, you have chosen a wrong version. Go through the installation process with caution again.

MinGW-w64 installation Problem: ERROR res

  • In some PC Windows, we have experienced a difficulty during MinGW-w64 installation.
  • It fails with ERROR res during the installation. I posted this question in the stackoverflow and got this answer. You may go their recommendation.
  • In summary, you install MSYS2 first, and then install MinGW-w64 as part of MSYS2.
    • MSYS2 installation is really easy and rarely fails.
    • It comes with a command-line package manager (pacman).
    • It offers always the newest MinGW-w64/GCC combo available.
    • You can also install many other packages compatible with this toolchain.
    • For details see this answer.
  • Don't forget adding the path <your MSYS2 root>/mingw64/bin to your PATH environment variable.

Using Mintty instead of cmd or PowerShell.

Install Atom.

  1. Atom is a text editor that most professional programmers love nowadays.

  2. Start Atom.

  3. Install some of essential packages recommended for C/C++ programmers listed below:

    • Platformio-ide-terminal
      • On successful installation, you will see a +sign at the bottom-left corner of the editor. Click + sign to open a console.
    • File-icons
    • Minimap
    • Markdown-preview
      • Open a rendered version of the Markdown in the current editor with ctrl-shift-m.
    • Autosave
      • It automatically saves files when the editors loses focus, are destroyed, or when the window is closed. Believe or not, it is disabled by default. You must check enabled in config setting or from the Autosave section of the Settings view.

    Themes of my personal preference:

    • UI Theme - Atom Dark,
    • Syntax Theme - Oceanic Next

    Note for Multi-screen users: If Atom is displayed off-screen, do the following:

    1. Alt + Tab to choose the atom window
    2. Alt + Space to open the context menu
    3. Press 'm' to select move
    4. Press any arrow key once
    5. Move your mouse (The misplaced window will follow your cursor.)

    Problem in platformio-ide-terminal: If the prompt does not show up in the terminal, you may look Issues #765 and #760 at github/platformio/platformio-atom-ide-terminal.

    1. #760 is a solution for Windows users.
    2. #765 includes a comment I posted. What I found is to follow the #760 solution except one item. Use apm instead of npm.

Install "GitHub Desktop" and "Git"

  • Install git from this site for your computer.
  • Install GitHub Desktop

After installation of GitHub Desktop, be a member if already not.

  • Clone the GitHub nowic repository into your local computer:

  • How to clone a repository from GitHub: Refer to this site.

  • Click 'watch' and 'star' at the top of the web page.

  • Then, in your computer, you may have the following github/nowic folder as shown below:

    C:\GitHub\nowic

  • Since this nowic repository can be updated anytime, keep this local repository as "read-only". Don't code yours here!.

  • Copy them into your own repository or your own local development folders in your computer you can easily access them. They should look like the following:

    ~/nowic/c++cc             # c++ for c coders
~/nowic/include           # include files
~/nowic/labs              # labs
~/nowic/lib               # nowic.lib, libnowic.a
~/nowic/src               # all source files except labs
~/nowic/psets             # problem sets - homework
    • For example: The pset01(problem set 01) folder provides you with a few files for your first homework assignment.
    ~/pset01/pset01.pdf       # this file
~/pset01/hellox.exe       # a solution to compare your work
~/pset01/names.txt        # a list of names used in Step 5.

    Note for Multi-screen users: Remove the following file if GitHub Desktop is displayed off-screen. Restart Desktop GitHub. (user below may be different in your system.)

    C:\Users\user\AppData\Roaming\GitHub Desktop\window-state.json

    JoyNote: How do I force git pull to overwrite local files?

    • Go to the ~/nowic folder.
    • Open a console and run the following two commands.
    git stash

    or

    git fetch --all
git reset --hard origin/master

    Explanation: git fetch downloads the latest from remote without trying to merge or rebase anything. Then the git reset resets the master branch to what you just fetched. The --hard option changes all the files in your working tree to match the files in origin/master Caution: If you have any local changes, they will be lost. With or without --hard option, any local commits that haven't been pushed will be lost.

    JoyNote: How do I keep my local files clean after trials?

    • Go to the ~/nowic folder.
    • Open a console and run the following command.
    git clean -f

    Explanation: To delete all untracked files.

Are ready for 'Hello World!' program in C++?

  • Open a console. (may use cmd or powershell)
    • You may use cmd or powershell at this point. Sooner or later, however, we are going to use a different kind of console called mintty. You may read UsingMinttyInMinGW.md for the Mintty installation at nowic folder.
  • Open hello.cpp file with Atom 
    Atom hello.cpp
  • Build an executable. The output name depends on your OS: hello.exe, a.exe for windows; hello.out, a.out for linux 
    g++ hello.cpp -o hello            # hello.exe or hello.out
g++ hello.cpp                     # a.exe or a.out
  • Run the executable. 
    ./hello                           # PowerShell
./a                               # PowerShell
hello                             # Cmd, Linux, OSX
a                                 # Cmd, Linux, OSX

Write Hello World! program

It is a tradition to write a Hello World! program when you learn a new programming language. The following program prints Hello World! on a console. Create a file with the following contents. Its file name is hello.cpp

// file: hello.cpp
#include <iostream>
using namespace std;

int main() {
    cout << "Hello World!";
}
  • // The line begins with two slashes is not a part of source code. This line will be excluded when the program runs.
  • #include The line begins with # is called a preprocessor directive. The preprocessor reads your program before it is compiled and only executes those lines beginning with a # symbol. When you send the file to the compiler, the preprocessor substitutes the #include with the contents of the specified file.
  • <iostream> The iostream file must be included since this program uses cout to display console output. This kind of file is called a header file. In this way you can create and use modules that define functions that you only add to your code when you need them. There are lots of different header files available for many different purposes.
  • using namespace std; C++ uses namespaces to organize the names of program entities. This line declares that the program will be accessing entities whose names are part of the namespace called std. Every name created by the iostream file is part of std namespace. In order for a program to use the entities such as cout in iostream, it must have access to the std namespace. You may rewrite hello.cpp as shown below:
// file: hello.cpp
#include <iostream>

int main() {
    std::cout << "Hello World!";
}

Observe two versions Hello World! program to see the difference. The difference is whether you are using the namespace or not.

Run hello.cpp program

To run the program, you must make an executable from the source code file, hello.cpp. We use the compiler to generate an executable (or runnable) file from the code in the source file. The executable file ends with .exe or .out extension as our source file ends with .cpp extension. We might compile the file as follows:

  • On the console, type the following line (without $) and press Enter key.
$ g++ hello.cpp         # generates a.exe, a.out
$ ./a.exe               # runs a.exe
$ ./a                   # runs a.exe, a.out
  • The line above compiles (and links) the source code and generates an executable called a.exe or a.out.
  • $ is a console prompt. (You don't need to enter it.)
  • The line above compiles (and links) the source code and generates an executable called a.exe
  • g++ is the name of our compiler, and # begins a command-line comment. We can run the executable file, a.exe or a.out, which will run our main function. If you want to name the executable, you may provide the file name with -.o option as follows:
$ g++ hello.cpp -o hello        # generates hello.exe
$ ./hello.exe                   # runs hello.exe
$ ./hello                       # runs hello.exe, hello.out

JoyNote:

  • Run hello.exe or hello.out without ./ in front, when you run it at Linux, OSX and mintty console^^.

Are ready to study more?

For further study of C or C++ basics, the following two video lectures in YouTube are recommended. A solid background in C will do good for C++ study in this course.

What's Next?

  • Watch Derek's lecture or more.
  • Read ArgcArgv.md. It may help you do the first problem set(pset).
  • Read UsingMintty.md at nowic and install Mintty console.

One thing I know, I was blind but now I see. John 9:25