Implement American Option And European Option In C++ assignment Help

/in , /by

Implement American Option And European Option In C++ assignment Help

P4/CMakeLists.txt

### CMake Version ############################################################# cmake_minimum_required(VERSION 3.10) ### Project Configuration ##################################################### get_filename_component(PROJECT_DIR_NAME ${CMAKE_CURRENT_LIST_DIR} NAME) string(REPLACE ” ” “_” PROJECT_DIR_NAME ${PROJECT_DIR_NAME}) project(${PROJECT_DIR_NAME} VERSION 1.0.0.0 # <major>.<minor>.<patch>.<tweak> LANGUAGES CXX) ### List of Files ############################################################# set(INCLUDE ${PROJECT_SOURCE_DIR}/include/std_lib_facilities.h ${PROJECT_SOURCE_DIR}/include/EuropeanOption.h ) set(INPUT_FILES ) set(OUTPUT_FILES ) set(SRC ${PROJECT_SOURCE_DIR}/src/EuropeanOption.cpp ${PROJECT_SOURCE_DIR}/src/main.cpp ) set(OTHER_FILES ) ### Compiler Flags ############################################################ # UNIX only if(NOT WIN32) # C++14 set(CMAKE_CXX_STANDARD 14) set(CMAKE_CXX_STANDARD_REQUIRED ON) set(CMAKE_CXX_EXTENSIONS OFF) # Common Flags set(CMAKE_CXX_FLAGS “${CMAKE_CXX_FLAGS} -Wall -fexceptions -pedantic-errors”) # Debug Flags set(CMAKE_CXX_FLAGS_DEBUG “-g -DDEBUG”) # Release Flags # -O2 instead of -O3 # -ftlo stands for Link Time Optimization (LTO) set(CMAKE_CXX_FLAGS_RELEASE “-O2 -DNDEBUG -flto”) # GCC (Ubuntu 18.04 LTS Bionic Beaver) if(UNIX AND NOT APPLE) set(CMAKE_CXX_FLAGS “${CMAKE_CXX_FLAGS}”) endif(UNIX AND NOT APPLE) # Clang (macOS Mojave 10.14) # -Wno-tautological-compare is required when using std_lib_facilities on macOS if(APPLE) set(CMAKE_CXX_FLAGS “${CMAKE_CXX_FLAGS} -Wno-tautological-compare”) endif(APPLE) endif(NOT WIN32) ### Build Types ############################################################### # UNIX only if(NOT WIN32) # if no build type is set, the default is Debug if(NOT CMAKE_BUILD_TYPE) set(CMAKE_BUILD_TYPE Debug) endif(NOT CMAKE_BUILD_TYPE) set(CMAKE_RUNTIME_OUTPUT_DIRECTORY ${PROJECT_BINARY_DIR}/${CMAKE_BUILD_TYPE}) endif(NOT WIN32) ### Build Configuration ####################################################### add_executable(${PROJECT_NAME} ${INCLUDE} ${INPUT_FILES} ${OUTPUT_FILES} ${SRC} ${OTHER_FILES}) target_include_directories(${PROJECT_NAME} PRIVATE ${PROJECT_SOURCE_DIR}/include) ###############################################################################

__MACOSX/P4/._CMakeLists.txt

P4/.DS_Store

__MACOSX/P4/._.DS_Store

P4/include/std_lib_facilities.h

/* std_lib_facilities.h */ /* Simple “Programming: Principles and Practice using C++ (second edition)” course header to be used for the first few weeks. It provides the most common standard headers (in the global namespace) and minimal exception/error support. Students: please don’t try to understand the details of headers just yet. All will be explained. This header is primarily used so that you don’t have to understand every concept all at once. By Chapter 10, you don’t need this file and after Chapter 21, you’ll understand it Revised April 25, 2010: simple_error() added Revised November 25 2013: remove support for pre-C++11 compilers, use C++11: <chrono> Revised November 28 2013: add a few container algorithms Revised June 8 2014: added #ifndef to workaround Microsoft C++11 weakness */ #pragma once #include <algorithm> #include <array> #include <cmath> #include <cstdlib> #include <forward_list> #include <fstream> #include <iomanip> #include <iostream> #include <list> #include <random> #include <regex> #include <sstream> #include <stdexcept> #include <string> #include <unordered_map> #include <vector> //—————————————————————————— //—————————————————————————— typedef long Unicode; //—————————————————————————— using namespace std; template <class T> string to_string(const T& t) { ostringstream os; os << t; return os.str(); } struct Range_error : out_of_range { // enhanced vector range error reporting int index; Range_error(int i) : out_of_range(“Range error: ” + to_string(i)) , index(i) { } }; // trivially range-checked vector (no iterator checking): template <class T> struct Vector : public std::vector<T> { using size_type = typename std::vector<T>::size_type; #ifdef _MSC_VER // microsoft doesn’t yet support C++11 inheriting constructors Vector() {} explicit Vector(size_type n) : std::vector<T>(n) { } Vector(size_type n, const T& v) : std::vector<T>(n, v) { } template <class I> Vector(I first, I last) : std::vector<T>(first, last) { } Vector(initializer_list<T> list) : std::vector<T>(list) { } #else using std::vector<T>::vector; // inheriting constructor #endif T& operator[](unsigned int i) // rather than return at(i); { if (i < 0 || this->size() <= i) throw Range_error(i); return std::vector<T>::operator[](i); } const T& operator[](unsigned int i) const { if (i < 0 || this->size() <= i) throw Range_error(i); return std::vector<T>::operator[](i); } }; // disgusting macro hack to get a range checked vector: #define vector Vector // trivially range-checked string (no iterator checking): struct String : std::string { using size_type = std::string::size_type; // using string::string; char& operator[](unsigned int i) // rather than return at(i); { if (i < 0 || size() <= i) throw Range_error(i); return std::string::operator[](i); } const char& operator[](unsigned int i) const { if (i < 0 || size() <= i) throw Range_error(i); return std::string::operator[](i); } }; namespace std { template <> struct hash<String> { size_t operator()(const String& s) const { return hash<std::string>()(s); } }; } // of namespace std struct Exit : runtime_error { Exit() : runtime_error(“Exit”) { } }; // error() simply disguises throws: inline void error(const string& s) { throw runtime_error(s); } inline void error(const string& s, const string& s2) { error(s + s2); } inline void error(const string& s, int i) { ostringstream os; os << s << “: ” << i; error(os.str()); } template <class T> char* as_bytes(T& i) // needed for binary I/O { void* addr = &i; // get the address of the first byte // of memory used to store the object return static_cast<char*>(addr); // treat that memory as bytes } // added by https://thiagowinkler.github.io inline void cin_clear() { if (cin.fail()) { cin.clear(); cin.ignore(numeric_limits<streamsize>::max(), ‘\n’); } } inline void keep_window_open() { cin.clear(); cout << “Please enter a character to exit\n”; char ch; cin >> ch; return; } inline void keep_window_open(string s) { if (s == “”) return; cin.clear(); cin.ignore(120, ‘\n’); for (;;) { cout << “Please enter ” << s << ” to exit\n”; string ss; while (cin >> ss && ss != s) cout << “Please enter ” << s << ” to exit\n”; return; } } // error function to be used (only) until error() is introduced in Chapter 5: inline void simple_error(string s) // write “error: s and exit program { cerr << “error: ” << s << ‘\n’; keep_window_open(); // for some Windows environments exit(1); } // make std::min() and std::max() accessible on systems with antisocial macros: #undef min #undef max // run-time checked narrowing cast (type conversion). See ???. template <class R, class A> R narrow_cast(const A& a) { R r = R(a); if (A(r) != a) error(string(“info loss”)); return r; } // random number generators. See 24.7. inline int randint(int min, int max) { static default_random_engine ran; return uniform_int_distribution<>{ min, max }(ran); } inline int randint(int max) { return randint(0, max); } //inline double sqrt(int x) { return sqrt(double(x)); } // to match C++0x // container algorithms. See 21.9. template <typename C> using Value_type = typename C::value_type; template <typename C> using Iterator = typename C::iterator; template <typename C> // requires Container<C>() void sort(C& c) { std::sort(c.begin(), c.end()); } template <typename C, typename Pred> // requires Container<C>() && Binary_Predicate<Value_type<C>>() void sort(C& c, Pred p) { std::sort(c.begin(), c.end(), p); } template <typename C, typename Val> // requires Container<C>() && Equality_comparable<C,Val>() Iterator<C> find(C& c, Val v) { return std::find(c.begin(), c.end(), v); } template <typename C, typename Pred> // requires Container<C>() && Predicate<Pred,Value_type<C>>() Iterator<C> find_if(C& c, Pred p) { return std::find_if(c.begin(), c.end(), p); }

__MACOSX/P4/include/._std_lib_facilities.h

P4/include/EuropeanOption.h

#pragma once #include “std_lib_facilities.h” class EuropeanOption { public: // Regular constructor EuropeanOption(string type, double spotPrice, double strikePrice, double interestRate, double volatility, double timeToMaturity); double getPrice(); private: string m_type; double m_spotPrice; double m_strikePrice; double m_interestRate; double m_volatility; double m_timeToMaturity; // Normal CDF double N(double value); };

__MACOSX/P4/include/._EuropeanOption.h

__MACOSX/P4/._include

P4/build/.DS_Store

__MACOSX/P4/build/._.DS_Store

P4/build/compile_commands.json

[ { “directory”: “/Users/zewenru/Desktop/2018Fall_A1Solution/P4/build”, “command”: “/usr/bin/clang++ -I/Users/zewenru/Desktop/2018Fall_A1Solution/P4/include -Wall -fexceptions -pedantic-errors -Wno-tautological-compare -g -DDEBUG -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -std=c++14 -o CMakeFiles/P4.dir/src/EuropeanOption.cpp.o -c /Users/zewenru/Desktop/2018Fall_A1Solution/P4/src/EuropeanOption.cpp”, “file”: “/Users/zewenru/Desktop/2018Fall_A1Solution/P4/src/EuropeanOption.cpp” }, { “directory”: “/Users/zewenru/Desktop/2018Fall_A1Solution/P4/build”, “command”: “/usr/bin/clang++ -I/Users/zewenru/Desktop/2018Fall_A1Solution/P4/include -Wall -fexceptions -pedantic-errors -Wno-tautological-compare -g -DDEBUG -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -std=c++14 -o CMakeFiles/P4.dir/src/main.cpp.o -c /Users/zewenru/Desktop/2018Fall_A1Solution/P4/src/main.cpp”, “file”: “/Users/zewenru/Desktop/2018Fall_A1Solution/P4/src/main.cpp” } ]

P4/build/CMakeFiles/cmake.check_cache

# This file is generated by cmake for dependency checking of the CMakeCache.txt file

P4/build/CMakeFiles/CMakeOutput.log

The system is: Darwin – 18.2.0 – x86_64 Compiling the CXX compiler identification source file “CMakeCXXCompilerId.cpp” succeeded. Compiler: /usr/bin/clang++ Build flags: Id flags: The output was: 0 Compilation of the CXX compiler identification source “CMakeCXXCompilerId.cpp” produced “a.out” The CXX compiler identification is AppleClang, found in “/Users/zewenru/Desktop/2018Fall_A1Solution/P4/build/CMakeFiles/3.12.1/CompilerIdCXX/a.out” Determining if the CXX compiler works passed with the following output: Change Dir: /Users/zewenru/Desktop/2018Fall_A1Solution/P4/build/CMakeFiles/CMakeTmp Run Build Command:”/usr/bin/make” “cmTC_73290/fast” /Library/Developer/CommandLineTools/usr/bin/make -f CMakeFiles/cmTC_73290.dir/build.make CMakeFiles/cmTC_73290.dir/build Building CXX object CMakeFiles/cmTC_73290.dir/testCXXCompiler.cxx.o /usr/bin/clang++ -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -o CMakeFiles/cmTC_73290.dir/testCXXCompiler.cxx.o -c /Users/zewenru/Desktop/2018Fall_A1Solution/P4/build/CMakeFiles/CMakeTmp/testCXXCompiler.cxx Linking CXX executable cmTC_73290 /usr/local/Cellar/cmake/3.12.1/bin/cmake -E cmake_link_script CMakeFiles/cmTC_73290.dir/link.txt –verbose=1 /usr/bin/clang++ -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -Wl,-search_paths_first -Wl,-headerpad_max_install_names CMakeFiles/cmTC_73290.dir/testCXXCompiler.cxx.o -o cmTC_73290 Detecting CXX compiler ABI info compiled with the following output: Change Dir: /Users/zewenru/Desktop/2018Fall_A1Solution/P4/build/CMakeFiles/CMakeTmp Run Build Command:”/usr/bin/make” “cmTC_32992/fast” /Library/Developer/CommandLineTools/usr/bin/make -f CMakeFiles/cmTC_32992.dir/build.make CMakeFiles/cmTC_32992.dir/build Building CXX object CMakeFiles/cmTC_32992.dir/CMakeCXXCompilerABI.cpp.o /usr/bin/clang++ -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -o CMakeFiles/cmTC_32992.dir/CMakeCXXCompilerABI.cpp.o -c /usr/local/Cellar/cmake/3.12.1/share/cmake/Modules/CMakeCXXCompilerABI.cpp Linking CXX executable cmTC_32992 /usr/local/Cellar/cmake/3.12.1/bin/cmake -E cmake_link_script CMakeFiles/cmTC_32992.dir/link.txt –verbose=1 /usr/bin/clang++ -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -Wl,-search_paths_first -Wl,-headerpad_max_install_names -v -Wl,-v CMakeFiles/cmTC_32992.dir/CMakeCXXCompilerABI.cpp.o -o cmTC_32992 Apple LLVM version 10.0.0 (clang-1000.10.44.4) Target: x86_64-apple-darwin18.2.0 Thread model: posix InstalledDir: /Library/Developer/CommandLineTools/usr/bin “/Library/Developer/CommandLineTools/usr/bin/ld” -demangle -lto_library /Library/Developer/CommandLineTools/usr/lib/libLTO.dylib -dynamic -arch x86_64 -macosx_version_min 10.14.0 -syslibroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -o cmTC_32992 -search_paths_first -headerpad_max_install_names -v CMakeFiles/cmTC_32992.dir/CMakeCXXCompilerABI.cpp.o -lc++ -lSystem /Library/Developer/CommandLineTools/usr/lib/clang/10.0.0/lib/darwin/libclang_rt.osx.a @(#)PROGRAM:ld PROJECT:ld64-409.12 BUILD 17:47:51 Sep 25 2018 configured to support archs: armv6 armv7 armv7s arm64 i386 x86_64 x86_64h armv6m armv7k armv7m armv7em Library search paths: /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/lib Framework search paths: /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/ Parsed CXX implicit link information from above output: link line regex: [^( *|.*[/\])(ld|CMAKE_LINK_STARTFILE-NOTFOUND|([^/\]+-)?ld|collect2)[^/\]*( |$)] ignore line: [Change Dir: /Users/zewenru/Desktop/2018Fall_A1Solution/P4/build/CMakeFiles/CMakeTmp] ignore line: [] ignore line: [Run Build Command:”/usr/bin/make” “cmTC_32992/fast”] ignore line: [/Library/Developer/CommandLineTools/usr/bin/make -f CMakeFiles/cmTC_32992.dir/build.make CMakeFiles/cmTC_32992.dir/build] ignore line: [Building CXX object CMakeFiles/cmTC_32992.dir/CMakeCXXCompilerABI.cpp.o] ignore line: [/usr/bin/clang++ -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -o CMakeFiles/cmTC_32992.dir/CMakeCXXCompilerABI.cpp.o -c /usr/local/Cellar/cmake/3.12.1/share/cmake/Modules/CMakeCXXCompilerABI.cpp] ignore line: [Linking CXX executable cmTC_32992] ignore line: [/usr/local/Cellar/cmake/3.12.1/bin/cmake -E cmake_link_script CMakeFiles/cmTC_32992.dir/link.txt –verbose=1] ignore line: [/usr/bin/clang++ -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -Wl,-search_paths_first -Wl,-headerpad_max_install_names -v -Wl,-v CMakeFiles/cmTC_32992.dir/CMakeCXXCompilerABI.cpp.o -o cmTC_32992 ] ignore line: [Apple LLVM version 10.0.0 (clang-1000.10.44.4)] ignore line: [Target: x86_64-apple-darwin18.2.0] ignore line: [Thread model: posix] ignore line: [InstalledDir: /Library/Developer/CommandLineTools/usr/bin] link line: [ “/Library/Developer/CommandLineTools/usr/bin/ld” -demangle -lto_library /Library/Developer/CommandLineTools/usr/lib/libLTO.dylib -dynamic -arch x86_64 -macosx_version_min 10.14.0 -syslibroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -o cmTC_32992 -search_paths_first -headerpad_max_install_names -v CMakeFiles/cmTC_32992.dir/CMakeCXXCompilerABI.cpp.o -lc++ -lSystem /Library/Developer/CommandLineTools/usr/lib/clang/10.0.0/lib/darwin/libclang_rt.osx.a] arg [/Library/Developer/CommandLineTools/usr/bin/ld] ==> ignore arg [-demangle] ==> ignore arg [-lto_library] ==> ignore, skip following value arg [/Library/Developer/CommandLineTools/usr/lib/libLTO.dylib] ==> skip value of -lto_library arg [-dynamic] ==> ignore arg [-arch] ==> ignore arg [x86_64] ==> ignore arg [-macosx_version_min] ==> ignore arg [10.14.0] ==> ignore arg [-syslibroot] ==> ignore arg [/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk] ==> ignore arg [-o] ==> ignore arg [cmTC_32992] ==> ignore arg [-search_paths_first] ==> ignore arg [-headerpad_max_install_names] ==> ignore arg [-v] ==> ignore arg [CMakeFiles/cmTC_32992.dir/CMakeCXXCompilerABI.cpp.o] ==> ignore arg [-lc++] ==> lib [c++] arg [-lSystem] ==> lib [System] arg [/Library/Developer/CommandLineTools/usr/lib/clang/10.0.0/lib/darwin/libclang_rt.osx.a] ==> lib [/Library/Developer/CommandLineTools/usr/lib/clang/10.0.0/lib/darwin/libclang_rt.osx.a] Library search paths: [;/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/lib] Framework search paths: [;/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/] remove lib [System] remove lib [/Library/Developer/CommandLineTools/usr/lib/clang/10.0.0/lib/darwin/libclang_rt.osx.a] collapse library dir [/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/lib] ==> [/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/lib] collapse framework dir [/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/] ==> [/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/System/Library/Frameworks] implicit libs: [c++] implicit dirs: [/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/lib] implicit fwks: [/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/System/Library/Frameworks] Detecting CXX [-std=c++1z] compiler features compiled with the following output: Change Dir: /Users/zewenru/Desktop/2018Fall_A1Solution/P4/build/CMakeFiles/CMakeTmp Run Build Command:”/usr/bin/make” “cmTC_a520f/fast” /Library/Developer/CommandLineTools/usr/bin/make -f CMakeFiles/cmTC_a520f.dir/build.make CMakeFiles/cmTC_a520f.dir/build Building CXX object CMakeFiles/cmTC_a520f.dir/feature_tests.cxx.o /usr/bin/clang++ -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -std=c++1z -o CMakeFiles/cmTC_a520f.dir/feature_tests.cxx.o -c /Users/zewenru/Desktop/2018Fall_A1Solution/P4/build/CMakeFiles/feature_tests.cxx Linking CXX executable cmTC_a520f /usr/local/Cellar/cmake/3.12.1/bin/cmake -E cmake_link_script CMakeFiles/cmTC_a520f.dir/link.txt –verbose=1 /usr/bin/clang++ -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -Wl,-search_paths_first -Wl,-headerpad_max_install_names CMakeFiles/cmTC_a520f.dir/feature_tests.cxx.o -o cmTC_a520f Feature record: CXX_FEATURE:1cxx_aggregate_default_initializers Feature record: CXX_FEATURE:1cxx_alias_templates Feature record: CXX_FEATURE:1cxx_alignas Feature record: CXX_FEATURE:1cxx_alignof Feature record: CXX_FEATURE:1cxx_attributes Feature record: CXX_FEATURE:1cxx_attribute_deprecated Feature record: CXX_FEATURE:1cxx_auto_type Feature record: CXX_FEATURE:1cxx_binary_literals Feature record: CXX_FEATURE:1cxx_constexpr Feature record: CXX_FEATURE:1cxx_contextual_conversions Feature record: CXX_FEATURE:1cxx_decltype Feature record: CXX_FEATURE:1cxx_decltype_auto Feature record: CXX_FEATURE:1cxx_decltype_incomplete_return_types Feature record: CXX_FEATURE:1cxx_default_function_template_args Feature record: CXX_FEATURE:1cxx_defaulted_functions Feature record: CXX_FEATURE:1cxx_defaulted_move_initializers Feature record: CXX_FEATURE:1cxx_delegating_constructors Feature record: CXX_FEATURE:1cxx_deleted_functions Feature record: CXX_FEATURE:1cxx_digit_separators Feature record: CXX_FEATURE:1cxx_enum_forward_declarations Feature record: CXX_FEATURE:1cxx_explicit_conversions Feature record: CXX_FEATURE:1cxx_extended_friend_declarations Feature record: CXX_FEATURE:1cxx_extern_templates Feature record: CXX_FEATURE:1cxx_final Feature record: CXX_FEATURE:1cxx_func_identifier Feature record: CXX_FEATURE:1cxx_generalized_initializers Feature record: CXX_FEATURE:1cxx_generic_lambdas Feature record: CXX_FEATURE:1cxx_inheriting_constructors Feature record: CXX_FEATURE:1cxx_inline_namespaces Feature record: CXX_FEATURE:1cxx_lambdas Feature record: CXX_FEATURE:1cxx_lambda_init_captures Feature record: CXX_FEATURE:1cxx_local_type_template_args Feature record: CXX_FEATURE:1cxx_long_long_type Feature record: CXX_FEATURE:1cxx_noexcept Feature record: CXX_FEATURE:1cxx_nonstatic_member_init Feature record: CXX_FEATURE:1cxx_nullptr Feature record: CXX_FEATURE:1cxx_override Feature record: CXX_FEATURE:1cxx_range_for Feature record: CXX_FEATURE:1cxx_raw_string_literals Feature record: CXX_FEATURE:1cxx_reference_qualified_functions Feature record: CXX_FEATURE:1cxx_relaxed_constexpr Feature record: CXX_FEATURE:1cxx_return_type_deduction Feature record: CXX_FEATURE:1cxx_right_angle_brackets Feature record: CXX_FEATURE:1cxx_rvalue_references Feature record: CXX_FEATURE:1cxx_sizeof_member Feature record: CXX_FEATURE:1cxx_static_assert Feature record: CXX_FEATURE:1cxx_strong_enums Feature record: CXX_FEATURE:1cxx_template_template_parameters Feature record: CXX_FEATURE:1cxx_thread_local Feature record: CXX_FEATURE:1cxx_trailing_return_types Feature record: CXX_FEATURE:1cxx_unicode_literals Feature record: CXX_FEATURE:1cxx_uniform_initialization Feature record: CXX_FEATURE:1cxx_unrestricted_unions Feature record: CXX_FEATURE:1cxx_user_literals Feature record: CXX_FEATURE:1cxx_variable_templates Feature record: CXX_FEATURE:1cxx_variadic_macros Feature record: CXX_FEATURE:1cxx_variadic_templates Detecting CXX [-std=c++14] compiler features compiled with the following output: Change Dir: /Users/zewenru/Desktop/2018Fall_A1Solution/P4/build/CMakeFiles/CMakeTmp Run Build Command:”/usr/bin/make” “cmTC_8fc55/fast” /Library/Developer/CommandLineTools/usr/bin/make -f CMakeFiles/cmTC_8fc55.dir/build.make CMakeFiles/cmTC_8fc55.dir/build Building CXX object CMakeFiles/cmTC_8fc55.dir/feature_tests.cxx.o /usr/bin/clang++ -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -std=c++14 -o CMakeFiles/cmTC_8fc55.dir/feature_tests.cxx.o -c /Users/zewenru/Desktop/2018Fall_A1Solution/P4/build/CMakeFiles/feature_tests.cxx Linking CXX executable cmTC_8fc55 /usr/local/Cellar/cmake/3.12.1/bin/cmake -E cmake_link_script CMakeFiles/cmTC_8fc55.dir/link.txt –verbose=1 /usr/bin/clang++ -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -Wl,-search_paths_first -Wl,-headerpad_max_install_names CMakeFiles/cmTC_8fc55.dir/feature_tests.cxx.o -o cmTC_8fc55 Feature record: CXX_FEATURE:1cxx_aggregate_default_initializers Feature record: CXX_FEATURE:1cxx_alias_templates Feature record: CXX_FEATURE:1cxx_alignas Feature record: CXX_FEATURE:1cxx_alignof Feature record: CXX_FEATURE:1cxx_attributes Feature record: CXX_FEATURE:1cxx_attribute_deprecated Feature record: CXX_FEATURE:1cxx_auto_type Feature record: CXX_FEATURE:1cxx_binary_literals Feature record: CXX_FEATURE:1cxx_constexpr Feature record: CXX_FEATURE:1cxx_contextual_conversions Feature record: CXX_FEATURE:1cxx_decltype Feature record: CXX_FEATURE:1cxx_decltype_auto Feature record: CXX_FEATURE:1cxx_decltype_incomplete_return_types Feature record: CXX_FEATURE:1cxx_default_function_template_args Feature record: CXX_FEATURE:1cxx_defaulted_functions Feature record: CXX_FEATURE:1cxx_defaulted_move_initializers Feature record: CXX_FEATURE:1cxx_delegating_constructors Feature record: CXX_FEATURE:1cxx_deleted_functions Feature record: CXX_FEATURE:1cxx_digit_separators Feature record: CXX_FEATURE:1cxx_enum_forward_declarations Feature record: CXX_FEATURE:1cxx_explicit_conversions Feature record: CXX_FEATURE:1cxx_extended_friend_declarations Feature record: CXX_FEATURE:1cxx_extern_templates Feature record: CXX_FEATURE:1cxx_final Feature record: CXX_FEATURE:1cxx_func_identifier Feature record: CXX_FEATURE:1cxx_generalized_initializers Feature record: CXX_FEATURE:1cxx_generic_lambdas Feature record: CXX_FEATURE:1cxx_inheriting_constructors Feature record: CXX_FEATURE:1cxx_inline_namespaces Feature record: CXX_FEATURE:1cxx_lambdas Feature record: CXX_FEATURE:1cxx_lambda_init_captures Feature record: CXX_FEATURE:1cxx_local_type_template_args Feature record: CXX_FEATURE:1cxx_long_long_type Feature record: CXX_FEATURE:1cxx_noexcept Feature record: CXX_FEATURE:1cxx_nonstatic_member_init Feature record: CXX_FEATURE:1cxx_nullptr Feature record: CXX_FEATURE:1cxx_override Feature record: CXX_FEATURE:1cxx_range_for Feature record: CXX_FEATURE:1cxx_raw_string_literals Feature record: CXX_FEATURE:1cxx_reference_qualified_functions Feature record: CXX_FEATURE:1cxx_relaxed_constexpr Feature record: CXX_FEATURE:1cxx_return_type_deduction Feature record: CXX_FEATURE:1cxx_right_angle_brackets Feature record: CXX_FEATURE:1cxx_rvalue_references Feature record: CXX_FEATURE:1cxx_sizeof_member Feature record: CXX_FEATURE:1cxx_static_assert Feature record: CXX_FEATURE:1cxx_strong_enums Feature record: CXX_FEATURE:1cxx_template_template_parameters Feature record: CXX_FEATURE:1cxx_thread_local Feature record: CXX_FEATURE:1cxx_trailing_return_types Feature record: CXX_FEATURE:1cxx_unicode_literals Feature record: CXX_FEATURE:1cxx_uniform_initialization Feature record: CXX_FEATURE:1cxx_unrestricted_unions Feature record: CXX_FEATURE:1cxx_user_literals Feature record: CXX_FEATURE:1cxx_variable_templates Feature record: CXX_FEATURE:1cxx_variadic_macros Feature record: CXX_FEATURE:1cxx_variadic_templates Detecting CXX [-std=c++11] compiler features compiled with the following output: Change Dir: /Users/zewenru/Desktop/2018Fall_A1Solution/P4/build/CMakeFiles/CMakeTmp Run Build Command:”/usr/bin/make” “cmTC_e42db/fast” /Library/Developer/CommandLineTools/usr/bin/make -f CMakeFiles/cmTC_e42db.dir/build.make CMakeFiles/cmTC_e42db.dir/build Building CXX object CMakeFiles/cmTC_e42db.dir/feature_tests.cxx.o /usr/bin/clang++ -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -std=c++11 -o CMakeFiles/cmTC_e42db.dir/feature_tests.cxx.o -c /Users/zewenru/Desktop/2018Fall_A1Solution/P4/build/CMakeFiles/feature_tests.cxx Linking CXX executable cmTC_e42db /usr/local/Cellar/cmake/3.12.1/bin/cmake -E cmake_link_script CMakeFiles/cmTC_e42db.dir/link.txt –verbose=1 /usr/bin/clang++ -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -Wl,-search_paths_first -Wl,-headerpad_max_install_names CMakeFiles/cmTC_e42db.dir/feature_tests.cxx.o -o cmTC_e42db Feature record: CXX_FEATURE:0cxx_aggregate_default_initializers Feature record: CXX_FEATURE:1cxx_alias_templates Feature record: CXX_FEATURE:1cxx_alignas Feature record: CXX_FEATURE:1cxx_alignof Feature record: CXX_FEATURE:1cxx_attributes Feature record: CXX_FEATURE:0cxx_attribute_deprecated Feature record: CXX_FEATURE:1cxx_auto_type Feature record: CXX_FEATURE:0cxx_binary_literals Feature record: CXX_FEATURE:1cxx_constexpr Feature record: CXX_FEATURE:0cxx_contextual_conversions Feature record: CXX_FEATURE:1cxx_decltype Feature record: CXX_FEATURE:0cxx_decltype_auto Feature record: CXX_FEATURE:1cxx_decltype_incomplete_return_types Feature record: CXX_FEATURE:1cxx_default_function_template_args Feature record: CXX_FEATURE:1cxx_defaulted_functions Feature record: CXX_FEATURE:1cxx_defaulted_move_initializers Feature record: CXX_FEATURE:1cxx_delegating_constructors Feature record: CXX_FEATURE:1cxx_deleted_functions Feature record: CXX_FEATURE:0cxx_digit_separators Feature record: CXX_FEATURE:1cxx_enum_forward_declarations Feature record: CXX_FEATURE:1cxx_explicit_conversions Feature record: CXX_FEATURE:1cxx_extended_friend_declarations Feature record: CXX_FEATURE:1cxx_extern_templates Feature record: CXX_FEATURE:1cxx_final Feature record: CXX_FEATURE:1cxx_func_identifier Feature record: CXX_FEATURE:1cxx_generalized_initializers Feature record: CXX_FEATURE:0cxx_generic_lambdas Feature record: CXX_FEATURE:1cxx_inheriting_constructors Feature record: CXX_FEATURE:1cxx_inline_namespaces Feature record: CXX_FEATURE:1cxx_lambdas Feature record: CXX_FEATURE:0cxx_lambda_init_captures Feature record: CXX_FEATURE:1cxx_local_type_template_args Feature record: CXX_FEATURE:1cxx_long_long_type Feature record: CXX_FEATURE:1cxx_noexcept Feature record: CXX_FEATURE:1cxx_nonstatic_member_init Feature record: CXX_FEATURE:1cxx_nullptr Feature record: CXX_FEATURE:1cxx_override Feature record: CXX_FEATURE:1cxx_range_for Feature record: CXX_FEATURE:1cxx_raw_string_literals Feature record: CXX_FEATURE:1cxx_reference_qualified_functions Feature record: CXX_FEATURE:0cxx_relaxed_constexpr Feature record: CXX_FEATURE:0cxx_return_type_deduction Feature record: CXX_FEATURE:1cxx_right_angle_brackets Feature record: CXX_FEATURE:1cxx_rvalue_references Feature record: CXX_FEATURE:1cxx_sizeof_member Feature record: CXX_FEATURE:1cxx_static_assert Feature record: CXX_FEATURE:1cxx_strong_enums Feature record: CXX_FEATURE:1cxx_template_template_parameters Feature record: CXX_FEATURE:1cxx_thread_local Feature record: CXX_FEATURE:1cxx_trailing_return_types Feature record: CXX_FEATURE:1cxx_unicode_literals Feature record: CXX_FEATURE:1cxx_uniform_initialization Feature record: CXX_FEATURE:1cxx_unrestricted_unions Feature record: CXX_FEATURE:1cxx_user_literals Feature record: CXX_FEATURE:0cxx_variable_templates Feature record: CXX_FEATURE:1cxx_variadic_macros Feature record: CXX_FEATURE:1cxx_variadic_templates Detecting CXX [-std=c++98] compiler features compiled with the following output: Change Dir: /Users/zewenru/Desktop/2018Fall_A1Solution/P4/build/CMakeFiles/CMakeTmp Run Build Command:”/usr/bin/make” “cmTC_22d71/fast” /Library/Developer/CommandLineTools/usr/bin/make -f CMakeFiles/cmTC_22d71.dir/build.make CMakeFiles/cmTC_22d71.dir/build Building CXX object CMakeFiles/cmTC_22d71.dir/feature_tests.cxx.o /usr/bin/clang++ -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -std=c++98 -o CMakeFiles/cmTC_22d71.dir/feature_tests.cxx.o -c /Users/zewenru/Desktop/2018Fall_A1Solution/P4/build/CMakeFiles/feature_tests.cxx Linking CXX executable cmTC_22d71 /usr/local/Cellar/cmake/3.12.1/bin/cmake -E cmake_link_script CMakeFiles/cmTC_22d71.dir/link.txt –verbose=1 /usr/bin/clang++ -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -Wl,-search_paths_first -Wl,-headerpad_max_install_names CMakeFiles/cmTC_22d71.dir/feature_tests.cxx.o -o cmTC_22d71 Feature record: CXX_FEATURE:0cxx_aggregate_default_initializers Feature record: CXX_FEATURE:0cxx_alias_templates Feature record: CXX_FEATURE:0cxx_alignas Feature record: CXX_FEATURE:0cxx_alignof Feature record: CXX_FEATURE:0cxx_attributes Feature record: CXX_FEATURE:0cxx_attribute_deprecated Feature record: CXX_FEATURE:0cxx_auto_type Feature record: CXX_FEATURE:0cxx_binary_literals Feature record: CXX_FEATURE:0cxx_constexpr Feature record: CXX_FEATURE:0cxx_contextual_conversions Feature record: CXX_FEATURE:0cxx_decltype Feature record: CXX_FEATURE:0cxx_decltype_auto Feature record: CXX_FEATURE:0cxx_decltype_incomplete_return_types Feature record: CXX_FEATURE:0cxx_default_function_template_args Feature record: CXX_FEATURE:0cxx_defaulted_functions Feature record: CXX_FEATURE:0cxx_defaulted_move_initializers Feature record: CXX_FEATURE:0cxx_delegating_constructors Feature record: CXX_FEATURE:0cxx_deleted_functions Feature record: CXX_FEATURE:0cxx_digit_separators Feature record: CXX_FEATURE:0cxx_enum_forward_declarations Feature record: CXX_FEATURE:0cxx_explicit_conversions Feature record: CXX_FEATURE:0cxx_extended_friend_declarations Feature record: CXX_FEATURE:0cxx_extern_templates Feature record: CXX_FEATURE:0cxx_final Feature record: CXX_FEATURE:0cxx_func_identifier Feature record: CXX_FEATURE:0cxx_generalized_initializers Feature record: CXX_FEATURE:0cxx_generic_lambdas Feature record: CXX_FEATURE:0cxx_inheriting_constructors Feature record: CXX_FEATURE:0cxx_inline_namespaces Feature record: CXX_FEATURE:0cxx_lambdas Feature record: CXX_FEATURE:0cxx_lambda_init_captures Feature record: CXX_FEATURE:0cxx_local_type_template_args Feature record: CXX_FEATURE:0cxx_long_long_type Feature record: CXX_FEATURE:0cxx_noexcept Feature record: CXX_FEATURE:0cxx_nonstatic_member_init Feature record: CXX_FEATURE:0cxx_nullptr Feature record: CXX_FEATURE:0cxx_override Feature record: CXX_FEATURE:0cxx_range_for Feature record: CXX_FEATURE:0cxx_raw_string_literals Feature record: CXX_FEATURE:0cxx_reference_qualified_functions Feature record: CXX_FEATURE:0cxx_relaxed_constexpr Feature record: CXX_FEATURE:0cxx_return_type_deduction Feature record: CXX_FEATURE:0cxx_right_angle_brackets Feature record: CXX_FEATURE:0cxx_rvalue_references Feature record: CXX_FEATURE:0cxx_sizeof_member Feature record: CXX_FEATURE:0cxx_static_assert Feature record: CXX_FEATURE:0cxx_strong_enums Feature record: CXX_FEATURE:1cxx_template_template_parameters Feature record: CXX_FEATURE:0cxx_thread_local Feature record: CXX_FEATURE:0cxx_trailing_return_types Feature record: CXX_FEATURE:0cxx_unicode_literals Feature record: CXX_FEATURE:0cxx_uniform_initialization Feature record: CXX_FEATURE:0cxx_unrestricted_unions Feature record: CXX_FEATURE:0cxx_user_literals Feature record: CXX_FEATURE:0cxx_variable_templates Feature record: CXX_FEATURE:0cxx_variadic_macros Feature record: CXX_FEATURE:0cxx_variadic_templates

P4/build/CMakeFiles/P4.dir/DependInfo.cmake

# The set of languages for which implicit dependencies are needed: set(CMAKE_DEPENDS_LANGUAGES “CXX” ) # The set of files for implicit dependencies of each language: set(CMAKE_DEPENDS_CHECK_CXX “/Users/zewenru/Desktop/2018Fall_A1Solution/P4/src/EuropeanOption.cpp” “/Users/zewenru/Desktop/2018Fall_A1Solution/P4/build/CMakeFiles/P4.dir/src/EuropeanOption.cpp.o” “/Users/zewenru/Desktop/2018Fall_A1Solution/P4/src/main.cpp” “/Users/zewenru/Desktop/2018Fall_A1Solution/P4/build/CMakeFiles/P4.dir/src/main.cpp.o” ) set(CMAKE_CXX_COMPILER_ID “AppleClang”) # The include file search paths: set(CMAKE_CXX_TARGET_INCLUDE_PATH “../include” ) # Targets to which this target links. set(CMAKE_TARGET_LINKED_INFO_FILES ) # Fortran module output directory. set(CMAKE_Fortran_TARGET_MODULE_DIR “”)

P4/build/CMakeFiles/P4.dir/depend.internal

# CMAKE generated file: DO NOT EDIT! # Generated by “Unix Makefiles” Generator, CMake Version 3.12 CMakeFiles/P4.dir/src/EuropeanOption.cpp.o ../include/EuropeanOption.h ../include/std_lib_facilities.h /Users/zewenru/Desktop/2018Fall_A1Solution/P4/src/EuropeanOption.cpp CMakeFiles/P4.dir/src/main.cpp.o ../include/EuropeanOption.h ../include/std_lib_facilities.h /Users/zewenru/Desktop/2018Fall_A1Solution/P4/src/main.cpp

P4/build/CMakeFiles/P4.dir/depend.make

# CMAKE generated file: DO NOT EDIT! # Generated by “Unix Makefiles” Generator, CMake Version 3.12 CMakeFiles/P4.dir/src/EuropeanOption.cpp.o: ../include/EuropeanOption.h CMakeFiles/P4.dir/src/EuropeanOption.cpp.o: ../include/std_lib_facilities.h CMakeFiles/P4.dir/src/EuropeanOption.cpp.o: ../src/EuropeanOption.cpp CMakeFiles/P4.dir/src/main.cpp.o: ../include/EuropeanOption.h CMakeFiles/P4.dir/src/main.cpp.o: ../include/std_lib_facilities.h CMakeFiles/P4.dir/src/main.cpp.o: ../src/main.cpp

P4/build/CMakeFiles/P4.dir/cmake_clean.cmake

file(REMOVE_RECURSE “CMakeFiles/P4.dir/src/EuropeanOption.cpp.o” “CMakeFiles/P4.dir/src/main.cpp.o” “Debug/P4.pdb” “Debug/P4” ) # Per-language clean rules from dependency scanning. foreach(lang CXX) include(CMakeFiles/P4.dir/cmake_clean_${lang}.cmake OPTIONAL) endforeach()

P4/build/CMakeFiles/P4.dir/link.txt

/usr/bin/clang++ -Wall -fexceptions -pedantic-errors -Wno-tautological-compare -g -DDEBUG -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -Wl,-search_paths_first -Wl,-headerpad_max_install_names CMakeFiles/P4.dir/src/EuropeanOption.cpp.o CMakeFiles/P4.dir/src/main.cpp.o -o Debug/P4

P4/build/CMakeFiles/P4.dir/progress.make

CMAKE_PROGRESS_1 = 1 CMAKE_PROGRESS_2 = 2 CMAKE_PROGRESS_3 = 3

P4/build/CMakeFiles/P4.dir/CXX.includecache

#IncludeRegexLine: ^[ ]*[#%][ ]*(include|import)[ ]*[<“]([^”>]+)([“>]) #IncludeRegexScan: ^.*$ #IncludeRegexComplain: ^$ #IncludeRegexTransform: ../include/EuropeanOption.h std_lib_facilities.h ../include/std_lib_facilities.h ../include/std_lib_facilities.h algorithm – array – cmath – cstdlib – forward_list – fstream – iomanip – iostream – list – random – regex – sstream – stdexcept – string – unordered_map – vector – /Users/zewenru/Desktop/2018Fall_A1Solution/P4/src/EuropeanOption.cpp EuropeanOption.h /Users/zewenru/Desktop/2018Fall_A1Solution/P4/src/EuropeanOption.h /Users/zewenru/Desktop/2018Fall_A1Solution/P4/src/main.cpp EuropeanOption.h /Users/zewenru/Desktop/2018Fall_A1Solution/P4/src/EuropeanOption.h std_lib_facilities.h /Users/zewenru/Desktop/2018Fall_A1Solution/P4/src/std_lib_facilities.h

P4/build/CMakeFiles/P4.dir/build.make

# CMAKE generated file: DO NOT EDIT! # Generated by “Unix Makefiles” Generator, CMake Version 3.12 # Delete rule output on recipe failure. .DELETE_ON_ERROR: #============================================================================= # Special targets provided by cmake. # Disable implicit rules so canonical targets will work. .SUFFIXES: # Remove some rules from gmake that .SUFFIXES does not remove. SUFFIXES = .SUFFIXES: .hpux_make_needs_suffix_list # Suppress display of executed commands. $(VERBOSE).SILENT: # A target that is always out of date. cmake_force: .PHONY : cmake_force #============================================================================= # Set environment variables for the build. # The shell in which to execute make rules. SHELL = /bin/sh # The CMake executable. CMAKE_COMMAND = /usr/local/Cellar/cmake/3.12.1/bin/cmake # The command to remove a file. RM = /usr/local/Cellar/cmake/3.12.1/bin/cmake -E remove -f # Escaping for special characters. EQUALS = = # The top-level source directory on which CMake was run. CMAKE_SOURCE_DIR = /Users/zewenru/Desktop/2018Fall_A1Solution/P4 # The top-level build directory on which CMake was run. CMAKE_BINARY_DIR = /Users/zewenru/Desktop/2018Fall_A1Solution/P4/build # Include any dependencies generated for this target. include CMakeFiles/P4.dir/depend.make # Include the progress variables for this target. include CMakeFiles/P4.dir/progress.make # Include the compile flags for this target’s objects. include CMakeFiles/P4.dir/flags.make CMakeFiles/P4.dir/src/EuropeanOption.cpp.o: CMakeFiles/P4.dir/flags.make CMakeFiles/P4.dir/src/EuropeanOption.cpp.o: ../src/EuropeanOption.cpp @$(CMAKE_COMMAND) -E cmake_echo_color –switch=$(COLOR) –green –progress-dir=/Users/zewenru/Desktop/2018Fall_A1Solution/P4/build/CMakeFiles –progress-num=$(CMAKE_PROGRESS_1) “Building CXX object CMakeFiles/P4.dir/src/EuropeanOption.cpp.o” /usr/bin/clang++ $(CXX_DEFINES) $(CXX_INCLUDES) $(CXX_FLAGS) -o CMakeFiles/P4.dir/src/EuropeanOption.cpp.o -c /Users/zewenru/Desktop/2018Fall_A1Solution/P4/src/EuropeanOption.cpp CMakeFiles/P4.dir/src/EuropeanOption.cpp.i: cmake_force @$(CMAKE_COMMAND) -E cmake_echo_color –switch=$(COLOR) –green “Preprocessing CXX source to CMakeFiles/P4.dir/src/EuropeanOption.cpp.i” /usr/bin/clang++ $(CXX_DEFINES) $(CXX_INCLUDES) $(CXX_FLAGS) -E /Users/zewenru/Desktop/2018Fall_A1Solution/P4/src/EuropeanOption.cpp > CMakeFiles/P4.dir/src/EuropeanOption.cpp.i CMakeFiles/P4.dir/src/EuropeanOption.cpp.s: cmake_force @$(CMAKE_COMMAND) -E cmake_echo_color –switch=$(COLOR) –green “Compiling CXX source to assembly CMakeFiles/P4.dir/src/EuropeanOption.cpp.s” /usr/bin/clang++ $(CXX_DEFINES) $(CXX_INCLUDES) $(CXX_FLAGS) -S /Users/zewenru/Desktop/2018Fall_A1Solution/P4/src/EuropeanOption.cpp -o CMakeFiles/P4.dir/src/EuropeanOption.cpp.s CMakeFiles/P4.dir/src/main.cpp.o: CMakeFiles/P4.dir/flags.make CMakeFiles/P4.dir/src/main.cpp.o: ../src/main.cpp @$(CMAKE_COMMAND) -E cmake_echo_color –switch=$(COLOR) –green –progress-dir=/Users/zewenru/Desktop/2018Fall_A1Solution/P4/build/CMakeFiles –progress-num=$(CMAKE_PROGRESS_2) “Building CXX object CMakeFiles/P4.dir/src/main.cpp.o” /usr/bin/clang++ $(CXX_DEFINES) $(CXX_INCLUDES) $(CXX_FLAGS) -o CMakeFiles/P4.dir/src/main.cpp.o -c /Users/zewenru/Desktop/2018Fall_A1Solution/P4/src/main.cpp CMakeFiles/P4.dir/src/main.cpp.i: cmake_force @$(CMAKE_COMMAND) -E cmake_echo_color –switch=$(COLOR) –green “Preprocessing CXX source to CMakeFiles/P4.dir/src/main.cpp.i” /usr/bin/clang++ $(CXX_DEFINES) $(CXX_INCLUDES) $(CXX_FLAGS) -E /Users/zewenru/Desktop/2018Fall_A1Solution/P4/src/main.cpp > CMakeFiles/P4.dir/src/main.cpp.i CMakeFiles/P4.dir/src/main.cpp.s: cmake_force @$(CMAKE_COMMAND) -E cmake_echo_color –switch=$(COLOR) –green “Compiling CXX source to assembly CMakeFiles/P4.dir/src/main.cpp.s” /usr/bin/clang++ $(CXX_DEFINES) $(CXX_INCLUDES) $(CXX_FLAGS) -S /Users/zewenru/Desktop/2018Fall_A1Solution/P4/src/main.cpp -o CMakeFiles/P4.dir/src/main.cpp.s # Object files for target P4 P4_OBJECTS = \ “CMakeFiles/P4.dir/src/EuropeanOption.cpp.o” \ “CMakeFiles/P4.dir/src/main.cpp.o” # External object files for target P4 P4_EXTERNAL_OBJECTS = Debug/P4: CMakeFiles/P4.dir/src/EuropeanOption.cpp.o Debug/P4: CMakeFiles/P4.dir/src/main.cpp.o Debug/P4: CMakeFiles/P4.dir/build.make Debug/P4: CMakeFiles/P4.dir/link.txt @$(CMAKE_COMMAND) -E cmake_echo_color –switch=$(COLOR) –green –bold –progress-dir=/Users/zewenru/Desktop/2018Fall_A1Solution/P4/build/CMakeFiles –progress-num=$(CMAKE_PROGRESS_3) “Linking CXX executable Debug/P4” $(CMAKE_COMMAND) -E cmake_link_script CMakeFiles/P4.dir/link.txt –verbose=$(VERBOSE) # Rule to build all files generated by this target. CMakeFiles/P4.dir/build: Debug/P4 .PHONY : CMakeFiles/P4.dir/build CMakeFiles/P4.dir/clean: $(CMAKE_COMMAND) -P CMakeFiles/P4.dir/cmake_clean.cmake .PHONY : CMakeFiles/P4.dir/clean CMakeFiles/P4.dir/depend: cd /Users/zewenru/Desktop/2018Fall_A1Solution/P4/build && $(CMAKE_COMMAND) -E cmake_depends “Unix Makefiles” /Users/zewenru/Desktop/2018Fall_A1Solution/P4 /Users/zewenru/Desktop/2018Fall_A1Solution/P4 /Users/zewenru/Desktop/2018Fall_A1Solution/P4/build /Users/zewenru/Desktop/2018Fall_A1Solution/P4/build /Users/zewenru/Desktop/2018Fall_A1Solution/P4/build/CMakeFiles/P4.dir/DependInfo.cmake –color=$(COLOR) .PHONY : CMakeFiles/P4.dir/depend

P4/build/CMakeFiles/P4.dir/flags.make

# CMAKE generated file: DO NOT EDIT! # Generated by “Unix Makefiles” Generator, CMake Version 3.12 # compile CXX with /usr/bin/clang++ CXX_FLAGS = -Wall -fexceptions -pedantic-errors -Wno-tautological-compare -g -DDEBUG -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -std=c++14 CXX_DEFINES = CXX_INCLUDES = -I/Users/zewenru/Desktop/2018Fall_A1Solution/P4/include

P4/build/CMakeFiles/P4.dir/src/main.cpp.o

P4/build/CMakeFiles/P4.dir/src/EuropeanOption.cpp.o

P4/build/CMakeFiles/3.12.1/CMakeDetermineCompilerABI_CXX.bin

P4/build/CMakeFiles/3.12.1/CompilerIdCXX/a.out

P4/build/CMakeFiles/3.12.1/CompilerIdCXX/CMakeCXXCompilerId.cpp

P4/build/CMakeFiles/3.12.1/CompilerIdCXX/CMakeCXXCompilerId.cpp

/* This source file must have a .cpp extension so that all C++ compilers
recognize the extension without flags.  Borland does not know .cxx for
example.  */
#ifndef  __cplusplus
# error  "A C compiler has been selected for C++."
#endif

/* Version number components: V=Version, R=Revision, P=Patch
Version date components:   YYYY=Year, MM=Month,   DD=Day  */

#if  defined ( __COMO__ )
# define COMPILER_ID  "Comeau"
/* __COMO_VERSION__ = VRR */
# define COMPILER_VERSION_MAJOR DEC ( __COMO_VERSION__  /   100 )
# define COMPILER_VERSION_MINOR DEC ( __COMO_VERSION__  %   100 )

#elif  defined ( __INTEL_COMPILER )   ||  defined ( __ICC )
# define COMPILER_ID  "Intel"
#  if  defined ( _MSC_VER )
#  define SIMULATE_ID  "MSVC"
# endif
/* __INTEL_COMPILER = VRP */
# define COMPILER_VERSION_MAJOR DEC ( __INTEL_COMPILER / 100 )
# define COMPILER_VERSION_MINOR DEC ( __INTEL_COMPILER / 10   %   10 )
#  if  defined ( __INTEL_COMPILER_UPDATE )
#  define COMPILER_VERSION_PATCH DEC ( __INTEL_COMPILER_UPDATE )
#  else
#  define COMPILER_VERSION_PATCH DEC ( __INTEL_COMPILER    %   10 )
# endif
#  if  defined ( __INTEL_COMPILER_BUILD_DATE )
/* __INTEL_COMPILER_BUILD_DATE = YYYYMMDD */
#  define COMPILER_VERSION_TWEAK DEC ( __INTEL_COMPILER_BUILD_DATE )
# endif
#  if  defined ( _MSC_VER )
/* _MSC_VER = VVRR */
#  define SIMULATE_VERSION_MAJOR DEC ( _MSC_VER  /   100 )
#  define SIMULATE_VERSION_MINOR DEC ( _MSC_VER  %   100 )
# endif

#elif  defined ( __PATHCC__ )
# define COMPILER_ID  "PathScale"
# define COMPILER_VERSION_MAJOR DEC ( __PATHCC__ )
# define COMPILER_VERSION_MINOR DEC ( __PATHCC_MINOR__ )
#  if  defined ( __PATHCC_PATCHLEVEL__ )
#  define COMPILER_VERSION_PATCH DEC ( __PATHCC_PATCHLEVEL__ )
# endif

#elif  defined ( __BORLANDC__ )   &&  defined ( __CODEGEARC_VERSION__ )
# define COMPILER_ID  "Embarcadero"
# define COMPILER_VERSION_MAJOR HEX ( __CODEGEARC_VERSION__ >> 24   &   0x00FF )
# define COMPILER_VERSION_MINOR HEX ( __CODEGEARC_VERSION__ >> 16   &   0x00FF )
# define COMPILER_VERSION_PATCH DEC ( __CODEGEARC_VERSION__      &   0xFFFF )

#elif  defined ( __BORLANDC__ )
# define COMPILER_ID  "Borland"
/* __BORLANDC__ = 0xVRR */
# define COMPILER_VERSION_MAJOR HEX ( __BORLANDC__ >> 8 )
# define COMPILER_VERSION_MINOR HEX ( __BORLANDC__  &   0xFF )

#elif  defined ( __WATCOMC__ )   &&  __WATCOMC__  <   1200
# define COMPILER_ID  "Watcom"
/* __WATCOMC__ = VVRR */
# define COMPILER_VERSION_MAJOR DEC ( __WATCOMC__  /   100 )
# define COMPILER_VERSION_MINOR DEC (( __WATCOMC__  /   10 )   %   10 )
#  if   ( __WATCOMC__  %   10 )   >   0
#  define COMPILER_VERSION_PATCH DEC ( __WATCOMC__  %   10 )
# endif

#elif  defined ( __WATCOMC__ )
# define COMPILER_ID  "OpenWatcom"
/* __WATCOMC__ = VVRP + 1100 */
# define COMPILER_VERSION_MAJOR DEC (( __WATCOMC__  -   1100 )   /   100 )
# define COMPILER_VERSION_MINOR DEC (( __WATCOMC__  /   10 )   %   10 )
#  if   ( __WATCOMC__  %   10 )   >   0
#  define COMPILER_VERSION_PATCH DEC ( __WATCOMC__  %   10 )
# endif

#elif  defined ( __SUNPRO_CC )
# define COMPILER_ID  "SunPro"
#  if  __SUNPRO_CC  >=   0x5100
/* __SUNPRO_CC = 0xVRRP */
#  define COMPILER_VERSION_MAJOR HEX ( __SUNPRO_CC >> 12 )
#  define COMPILER_VERSION_MINOR HEX ( __SUNPRO_CC >> 4   &   0xFF )
#  define COMPILER_VERSION_PATCH HEX ( __SUNPRO_CC     &   0xF )
#  else
/* __SUNPRO_CC = 0xVRP */
#  define COMPILER_VERSION_MAJOR HEX ( __SUNPRO_CC >> 8 )
#  define COMPILER_VERSION_MINOR HEX ( __SUNPRO_CC >> 4   &   0xF )
#  define COMPILER_VERSION_PATCH HEX ( __SUNPRO_CC     &   0xF )
# endif

#elif  defined ( __HP_aCC )
# define COMPILER_ID  "HP"
/* __HP_aCC = VVRRPP */
# define COMPILER_VERSION_MAJOR DEC ( __HP_aCC / 10000 )
# define COMPILER_VERSION_MINOR DEC ( __HP_aCC / 100   %   100 )
# define COMPILER_VERSION_PATCH DEC ( __HP_aCC      %   100 )

#elif  defined ( __DECCXX )
# define COMPILER_ID  "Compaq"
/* __DECCXX_VER = VVRRTPPPP */
# define COMPILER_VERSION_MAJOR DEC ( __DECCXX_VER / 10000000 )
# define COMPILER_VERSION_MINOR DEC ( __DECCXX_VER / 100000    %   100 )
# define COMPILER_VERSION_PATCH DEC ( __DECCXX_VER          %   10000 )

#elif  defined ( __IBMCPP__ )   &&  defined ( __COMPILER_VER__ )
# define COMPILER_ID  "zOS"
#  if  defined ( __ibmxl__ )
#  define COMPILER_VERSION_MAJOR DEC ( __ibmxl_version__ )
#  define COMPILER_VERSION_MINOR DEC ( __ibmxl_release__ )
#  define COMPILER_VERSION_PATCH DEC ( __ibmxl_modification__ )
#  define COMPILER_VERSION_TWEAK DEC ( __ibmxl_ptf_fix_level__ )
#  else
/* __IBMCPP__ = VRP */
#  define COMPILER_VERSION_MAJOR DEC ( __IBMCPP__ / 100 )
#  define COMPILER_VERSION_MINOR DEC ( __IBMCPP__ / 10   %   10 )
#  define COMPILER_VERSION_PATCH DEC ( __IBMCPP__     %   10 )
# endif

#elif  defined ( __ibmxl__ )   ||   ( defined ( __IBMCPP__ )   &&   ! defined ( __COMPILER_VER__ )   &&  __IBMCPP__  >=   800 )
# define COMPILER_ID  "XL"
#  if  defined ( __ibmxl__ )
#  define COMPILER_VERSION_MAJOR DEC ( __ibmxl_version__ )
#  define COMPILER_VERSION_MINOR DEC ( __ibmxl_release__ )
#  define COMPILER_VERSION_PATCH DEC ( __ibmxl_modification__ )
#  define COMPILER_VERSION_TWEAK DEC ( __ibmxl_ptf_fix_level__ )
#  else
/* __IBMCPP__ = VRP */
#  define COMPILER_VERSION_MAJOR DEC ( __IBMCPP__ / 100 )
#  define COMPILER_VERSION_MINOR DEC ( __IBMCPP__ / 10   %   10 )
#  define COMPILER_VERSION_PATCH DEC ( __IBMCPP__     %   10 )
# endif

#elif  defined ( __IBMCPP__ )   &&   ! defined ( __COMPILER_VER__ )   &&  __IBMCPP__  <   800
# define COMPILER_ID  "VisualAge"
#  if  defined ( __ibmxl__ )
#  define COMPILER_VERSION_MAJOR DEC ( __ibmxl_version__ )
#  define COMPILER_VERSION_MINOR DEC ( __ibmxl_release__ )
#  define COMPILER_VERSION_PATCH DEC ( __ibmxl_modification__ )
#  define COMPILER_VERSION_TWEAK DEC ( __ibmxl_ptf_fix_level__ )
#  else
/* __IBMCPP__ = VRP */
#  define COMPILER_VERSION_MAJOR DEC ( __IBMCPP__ / 100 )
#  define COMPILER_VERSION_MINOR DEC ( __IBMCPP__ / 10   %   10 )
#  define COMPILER_VERSION_PATCH DEC ( __IBMCPP__     %   10 )
# endif

#elif  defined ( __PGI )
# define COMPILER_ID  "PGI"
# define COMPILER_VERSION_MAJOR DEC ( __PGIC__ )
# define COMPILER_VERSION_MINOR DEC ( __PGIC_MINOR__ )
#  if  defined ( __PGIC_PATCHLEVEL__ )
#  define COMPILER_VERSION_PATCH DEC ( __PGIC_PATCHLEVEL__ )
# endif

#elif  defined ( _CRAYC )
# define COMPILER_ID  "Cray"
# define COMPILER_VERSION_MAJOR DEC ( _RELEASE_MAJOR )
# define COMPILER_VERSION_MINOR DEC ( _RELEASE_MINOR )

#elif  defined ( __TI_COMPILER_VERSION__ )
# define COMPILER_ID  "TI"
/* __TI_COMPILER_VERSION__ = VVVRRRPPP */
# define COMPILER_VERSION_MAJOR DEC ( __TI_COMPILER_VERSION__ / 1000000 )
# define COMPILER_VERSION_MINOR DEC ( __TI_COMPILER_VERSION__ / 1000     %   1000 )
# define COMPILER_VERSION_PATCH DEC ( __TI_COMPILER_VERSION__         %   1000 )

#elif  defined ( __FUJITSU )   ||  defined ( __FCC_VERSION )   ||  defined ( __fcc_version )
# define COMPILER_ID  "Fujitsu"

#elif  defined ( __SCO_VERSION__ )
# define COMPILER_ID  "SCO"

#elif  defined ( __clang__ )   &&  defined ( __apple_build_version__ )
# define COMPILER_ID  "AppleClang"
#  if  defined ( _MSC_VER )
#  define SIMULATE_ID  "MSVC"
# endif
# define COMPILER_VERSION_MAJOR DEC ( __clang_major__ )
# define COMPILER_VERSION_MINOR DEC ( __clang_minor__ )
# define COMPILER_VERSION_PATCH DEC ( __clang_patchlevel__ )
#  if  defined ( _MSC_VER )
/* _MSC_VER = VVRR */
#  define SIMULATE_VERSION_MAJOR DEC ( _MSC_VER  /   100 )
#  define SIMULATE_VERSION_MINOR DEC ( _MSC_VER  %   100 )
# endif
# define COMPILER_VERSION_TWEAK DEC ( __apple_build_version__ )

#elif  defined ( __clang__ )
# define COMPILER_ID  "Clang"
#  if  defined ( _MSC_VER )
#  define SIMULATE_ID  "MSVC"
# endif
# define COMPILER_VERSION_MAJOR DEC ( __clang_major__ )
# define COMPILER_VERSION_MINOR DEC ( __clang_minor__ )
# define COMPILER_VERSION_PATCH DEC ( __clang_patchlevel__ )
#  if  defined ( _MSC_VER )
/* _MSC_VER = VVRR */
#  define SIMULATE_VERSION_MAJOR DEC ( _MSC_VER  /   100 )
#  define SIMULATE_VERSION_MINOR DEC ( _MSC_VER  %   100 )
# endif

#elif  defined ( __GNUC__ )   ||  defined ( __GNUG__ )
# define COMPILER_ID  "GNU"
#  if  defined ( __GNUC__ )
#  define COMPILER_VERSION_MAJOR DEC ( __GNUC__ )
#  else
#  define COMPILER_VERSION_MAJOR DEC ( __GNUG__ )
# endif
#  if  defined ( __GNUC_MINOR__ )
#  define COMPILER_VERSION_MINOR DEC ( __GNUC_MINOR__ )
# endif
#  if  defined ( __GNUC_PATCHLEVEL__ )
#  define COMPILER_VERSION_PATCH DEC ( __GNUC_PATCHLEVEL__ )
# endif

#elif  defined ( _MSC_VER )
# define COMPILER_ID  "MSVC"
/* _MSC_VER = VVRR */
# define COMPILER_VERSION_MAJOR DEC ( _MSC_VER  /   100 )
# define COMPILER_VERSION_MINOR DEC ( _MSC_VER  %   100 )
#  if  defined ( _MSC_FULL_VER )
#   if  _MSC_VER  >=   1400
/* _MSC_FULL_VER = VVRRPPPPP */
#   define COMPILER_VERSION_PATCH DEC ( _MSC_FULL_VER  %   100000 )
#   else
/* _MSC_FULL_VER = VVRRPPPP */
#   define COMPILER_VERSION_PATCH DEC ( _MSC_FULL_VER  %   10000 )
#  endif
# endif
#  if  defined ( _MSC_BUILD )
#  define COMPILER_VERSION_TWEAK DEC ( _MSC_BUILD )
# endif

#elif  defined ( __VISUALDSPVERSION__ )   ||  defined ( __ADSPBLACKFIN__ )   ||  defined ( __ADSPTS__ )   ||  defined ( __ADSP21000__ )
# define COMPILER_ID  "ADSP"
#if  defined ( __VISUALDSPVERSION__ )
/* __VISUALDSPVERSION__ = 0xVVRRPP00 */
# define COMPILER_VERSION_MAJOR HEX ( __VISUALDSPVERSION__ >> 24 )
# define COMPILER_VERSION_MINOR HEX ( __VISUALDSPVERSION__ >> 16   &   0xFF )
# define COMPILER_VERSION_PATCH HEX ( __VISUALDSPVERSION__ >> 8    &   0xFF )
#endif

#elif  defined ( __IAR_SYSTEMS_ICC__ )   ||  defined ( __IAR_SYSTEMS_ICC )
# define COMPILER_ID  "IAR"
#  if  defined ( __VER__ )
#  define COMPILER_VERSION_MAJOR DEC (( __VER__ )   /   1000000 )
#  define COMPILER_VERSION_MINOR DEC ((( __VER__ )   /   1000 )   %   1000 )
#  define COMPILER_VERSION_PATCH DEC (( __VER__ )   %   1000 )
#  define COMPILER_VERSION_INTERNAL DEC ( __IAR_SYSTEMS_ICC__ )
# endif

#elif  defined ( __ARMCC_VERSION )
# define COMPILER_ID  "ARMCC"
#if  __ARMCC_VERSION  >=   1000000
/* __ARMCC_VERSION = VRRPPPP */
# define COMPILER_VERSION_MAJOR DEC ( __ARMCC_VERSION / 1000000 )
# define COMPILER_VERSION_MINOR DEC ( __ARMCC_VERSION / 10000   %   100 )
# define COMPILER_VERSION_PATCH DEC ( __ARMCC_VERSION      %   10000 )
#else
/* __ARMCC_VERSION = VRPPPP */
# define COMPILER_VERSION_MAJOR DEC ( __ARMCC_VERSION / 100000 )
# define COMPILER_VERSION_MINOR DEC ( __ARMCC_VERSION / 10000   %   10 )
# define COMPILER_VERSION_PATCH DEC ( __ARMCC_VERSION     %   10000 )
#endif

#elif  defined ( _SGI_COMPILER_VERSION )   ||  defined ( _COMPILER_VERSION )
# define COMPILER_ID  "MIPSpro"
#  if  defined ( _SGI_COMPILER_VERSION )
/* _SGI_COMPILER_VERSION = VRP */
#  define COMPILER_VERSION_MAJOR DEC ( _SGI_COMPILER_VERSION / 100 )
#  define COMPILER_VERSION_MINOR DEC ( _SGI_COMPILER_VERSION / 10   %   10 )
#  define COMPILER_VERSION_PATCH DEC ( _SGI_COMPILER_VERSION     %   10 )
#  else
/* _COMPILER_VERSION = VRP */
#  define COMPILER_VERSION_MAJOR DEC ( _COMPILER_VERSION / 100 )
#  define COMPILER_VERSION_MINOR DEC ( _COMPILER_VERSION / 10   %   10 )
#  define COMPILER_VERSION_PATCH DEC ( _COMPILER_VERSION     %   10 )
# endif

/* These compilers are either not known or too old to define an
identification macro.  Try to identify the platform and guess that
it is the native compiler.  */
#elif  defined ( __sgi )
# define COMPILER_ID  "MIPSpro"

#elif  defined ( __hpux )   ||  defined ( __hpua )
# define COMPILER_ID  "HP"

#else   /* unknown compiler */
# define COMPILER_ID  ""
#endif

/* Construct the string literal in pieces to prevent the source from
getting matched.  Store it in a pointer rather than an array
because some compilers will just produce instructions to fill the
array rather than assigning a pointer to a static array.  */
char   const *  info_compiler  =   "INFO"   ":"   "compiler["  COMPILER_ID  "]" ;
#ifdef  SIMULATE_ID
char   const *  info_simulate  =   "INFO"   ":"   "simulate["  SIMULATE_ID  "]" ;
#endif

#ifdef  __QNXNTO__
char   const *  qnxnto  =   "INFO"   ":"   "qnxnto[]" ;
#endif

#if  defined ( __CRAYXE )   ||  defined ( __CRAYXC )
char   const   * info_cray  =   "INFO"   ":"   "compiler_wrapper[CrayPrgEnv]" ;
#endif

#define  STRINGIFY_HELPER ( X )  #X
#define  STRINGIFY ( X )  STRINGIFY_HELPER ( X )

/* Identify known platforms by name.  */
#if  defined ( __linux )   ||  defined ( __linux__ )   ||  defined ( linux )
# define PLATFORM_ID  "Linux"

#elif  defined ( __CYGWIN__ )
# define PLATFORM_ID  "Cygwin"

#elif  defined ( __MINGW32__ )
# define PLATFORM_ID  "MinGW"

#elif  defined ( __APPLE__ )
# define PLATFORM_ID  "Darwin"

#elif  defined ( _WIN32 )   ||  defined ( __WIN32__ )   ||  defined ( WIN32 )
# define PLATFORM_ID  "Windows"

#elif  defined ( __FreeBSD__ )   ||  defined ( __FreeBSD )
# define PLATFORM_ID  "FreeBSD"

#elif  defined ( __NetBSD__ )   ||  defined ( __NetBSD )
# define PLATFORM_ID  "NetBSD"

#elif  defined ( __OpenBSD__ )   ||  defined ( __OPENBSD )
# define PLATFORM_ID  "OpenBSD"

#elif  defined ( __sun )   ||  defined ( sun )
# define PLATFORM_ID  "SunOS"

#elif  defined ( _AIX )   ||  defined ( __AIX )   ||  defined ( __AIX__ )   ||  defined ( __aix )   ||  defined ( __aix__ )
# define PLATFORM_ID  "AIX"

#elif  defined ( __sgi )   ||  defined ( __sgi__ )   ||  defined ( _SGI )
# define PLATFORM_ID  "IRIX"

#elif  defined ( __hpux )   ||  defined ( __hpux__ )
# define PLATFORM_ID  "HP-UX"

#elif  defined ( __HAIKU__ )
# define PLATFORM_ID  "Haiku"

#elif  defined ( __BeOS )   ||  defined ( __BEOS__ )   ||  defined ( _BEOS )
# define PLATFORM_ID  "BeOS"

#elif  defined ( __QNX__ )   ||  defined ( __QNXNTO__ )
# define PLATFORM_ID  "QNX"

#elif  defined ( __tru64 )   ||  defined ( _tru64 )   ||  defined ( __TRU64__ )
# define PLATFORM_ID  "Tru64"

#elif  defined ( __riscos )   ||  defined ( __riscos__ )
# define PLATFORM_ID  "RISCos"

#elif  defined ( __sinix )   ||  defined ( __sinix__ )   ||  defined ( __SINIX__ )
# define PLATFORM_ID  "SINIX"

#elif  defined ( __UNIX_SV__ )
# define PLATFORM_ID  "UNIX_SV"

#elif  defined ( __bsdos__ )
# define PLATFORM_ID  "BSDOS"

#elif  defined ( _MPRAS )   ||  defined ( MPRAS )
# define PLATFORM_ID  "MP-RAS"

#elif  defined ( __osf )   ||  defined ( __osf__ )
# define PLATFORM_ID  "OSF1"

#elif  defined ( _SCO_SV )   ||  defined ( SCO_SV )   ||  defined ( sco_sv )
# define PLATFORM_ID  "SCO_SV"

#elif  defined ( __ultrix )   ||  defined ( __ultrix__ )   ||  defined ( _ULTRIX )
# define PLATFORM_ID  "ULTRIX"

#elif  defined ( __XENIX__ )   ||  defined ( _XENIX )   ||  defined ( XENIX )
# define PLATFORM_ID  "Xenix"

#elif  defined ( __WATCOMC__ )
#  if  defined ( __LINUX__ )
#  define PLATFORM_ID  "Linux"

# elif defined ( __DOS__ )
#  define PLATFORM_ID  "DOS"

# elif defined ( __OS2__ )
#  define PLATFORM_ID  "OS2"

 
Do you need a similar assignment done for you from scratch? Order now!
Use Discount Code "Newclient" for a 15% Discount!

Disaster -Assignment

/in , /by

 

Graded Assignments may be found at the end of each chapter of the required textbook under the title “Real-World Exercises”. Each assignment is due between Monday to Sunday evening by 11:59 p.m. EST. of the respective week. Each student is to select one exercise (per module exercise) from the grouping as identified below. Provide documented evidence, in Moodle, of completion of the chosen exercise (i.e. provide answers to each of the stated questions). Detailed and significant scholarly answers will be allotted full point value. Incomplete, inaccurate, or inadequate answers will receive less than full credit depending on the answers provided. All submissions need to directed to the appropriate area within Moodle. Late submissions, hardcopy, or email submissions will not be accepted.350 words 2 references

 
Do you need a similar assignment done for you from scratch? Order now!
Use Discount Code "Newclient" for a 15% Discount!

Computer Science homework help

/in , /by

Computer Science homework help

You will write a flowchart, and C code for a program that does the following:

1. Uses a “for” loop.

2. Asks the user for their age.

3. Prints “Happy Birthday” for every year of the user’s age, along with the year.

Here is what the output of the program looks like.

File Submission

Upload your Flowgorithm file, your .c file, and a screen shot of your code output saved in a Word document including the path name directory at the top of the screen into the dropbox for grading.

 
Do you need a similar assignment done for you from scratch? Order now!
Use Discount Code "Newclient" for a 15% Discount!

Nursing Paper Example on Gastrointestinal Disease: Gastroesophageal Reflux Disease (GORD)

/in , , , , , , /by

Nursing Paper Example on Gastrointestinal Disease: Gastroesophageal Reflux Disease (GORD)

Introduction

Gastroesophageal Reflux Disease (GORD) is a prevalent gastrointestinal ailment affecting millions worldwide. Characterized by the backward flow of stomach acid into the esophagus, GORD poses significant discomfort and potential health risks if left untreated. The lower esophageal sphincter’s weakened state allows gastric contents to regurgitate, causing symptoms like heartburn, chest pain, and regurgitation. While the exact prevalence varies across demographics, GORD is commonly associated with factors such as obesity, smoking, and certain medications. Understanding the underlying mechanisms of GORD is crucial for effective management and prevention of complications. This essay explores the causes, symptoms, etiology, pathophysiology, diagnosis, treatment regimens, and patient education strategies related to GORD, shedding light on its impact on individuals’ daily lives and the importance of comprehensive management approaches. (Nursing Paper Example on Gastrointestinal Disease: Gastroesophageal Reflux Disease (GORD))

Nursing Paper Example on Gastrointestinal Disease: Gastroesophageal Reflux Disease (GORD)

Causes

Gastroesophageal Reflux Disease (GORD) stems from various factors, primarily centered around the malfunctioning of the lower esophageal sphincter (LES), a muscular ring separating the esophagus from the stomach. This weakening or relaxation of the LES allows stomach acid and partially digested food to flow backward into the esophagus, leading to the characteristic symptoms of GORD.

One of the significant causes of LES dysfunction is obesity. Excess weight puts pressure on the abdomen, which can force stomach contents upward into the esophagus, particularly when lying down or bending over. Additionally, adipose tissue produces hormones and substances that may contribute to LES relaxation, exacerbating reflux symptoms in obese individuals.

Smoking is another prominent risk factor for GORD. The chemicals in cigarette smoke can weaken the LES and impair its ability to prevent acid reflux. Moreover, smoking reduces saliva production, which normally helps neutralize stomach acid in the esophagus. Consequently, smokers are more prone to experiencing severe and prolonged reflux symptoms.

Certain medications are known to exacerbate GORD symptoms or weaken the LES. These include nonsteroidal anti-inflammatory drugs (NSAIDs) like ibuprofen and aspirin, which can irritate the esophageal lining and increase acid production, aggravating reflux symptoms. Other medications, such as calcium channel blockers used to treat hypertension and some sedatives, may relax the LES, facilitating acid reflux.

Dietary factors play a crucial role in triggering GORD symptoms. Spicy, acidic, and fatty foods can irritate the esophagus and stimulate acid production, exacerbating reflux. Citrus fruits, tomatoes, chocolate, caffeine, and alcohol are common culprits known to worsen symptoms in susceptible individuals. Moreover, large meals and lying down shortly after eating can increase intra-abdominal pressure, promoting acid reflux.

Pregnancy is also associated with an increased risk of GORD due to hormonal changes and elevated intra-abdominal pressure as the uterus expands. Hormones like progesterone relax the LES, contributing to reflux symptoms during pregnancy. Additionally, the growing fetus can exert pressure on the stomach, forcing acid into the esophagus.

In summary, GORD is caused by a combination of factors, including obesity, smoking, certain medications, dietary habits, and pregnancy. Understanding these underlying causes is essential for developing effective management strategies tailored to individual patients and addressing modifiable risk factors to alleviate symptoms and improve quality of life. (Nursing Paper Example on Gastrointestinal Disease: Gastroesophageal Reflux Disease (GORD)

Signs and Symptoms

Heartburn:
Heartburn is the hallmark symptom of Gastroesophageal Reflux Disease (GORD), characterized by a burning sensation in the chest or throat. It typically occurs after eating or when lying down and is caused by stomach acid refluxing into the esophagus. Heartburn can range from mild discomfort to severe pain and is often exacerbated by certain foods, beverages, or lying flat.

Regurgitation:
Regurgitation is the involuntary return of partially digested food or stomach contents into the mouth or throat. Individuals with GORD may experience a sour or bitter taste in their mouth as stomach acid regurgitates into the esophagus. Regurgitation can occur shortly after eating or when bending over and is often accompanied by a sensation of fluid moving up the chest.

Chest Pain:
Chest pain, also known as acid indigestion, is a common symptom of GORD that can mimic heart-related conditions such as angina or a heart attack. The pain may be sharp or burning and is typically located behind the breastbone. It may worsen when lying down or after consuming acidic or fatty foods. While chest pain in GORD is usually non-cardiac in nature, it should be evaluated by a healthcare professional to rule out serious cardiac conditions.

Difficulty Swallowing:
Some individuals with GORD may experience dysphagia, or difficulty swallowing, due to inflammation and irritation of the esophagus caused by acid reflux. Dysphagia can manifest as a sensation of food sticking in the throat or chest, discomfort or pain while swallowing, or the need to swallow repeatedly to move food down. Severe dysphagia may indicate complications such as esophageal strictures or narrowing.

Persistent Cough:
A chronic cough that persists despite treatment for other respiratory conditions may be a symptom of GORD. The reflux of stomach acid into the esophagus can irritate the throat and trigger coughing. This cough is often dry and persistent, particularly at night or after eating. While coughing is a common symptom of GORD, it can also be indicative of other respiratory or gastrointestinal disorders, necessitating proper evaluation by a healthcare provider.

In conclusion, GORD manifests through various signs and symptoms, including heartburn, regurgitation, chest pain, difficulty swallowing, and persistent cough. These symptoms can significantly impact an individual’s quality of life and may vary in severity depending on the frequency and extent of acid reflux. Recognizing these manifestations is crucial for timely diagnosis and management of GORD to alleviate discomfort and prevent complications. (Nursing Paper Example on Gastrointestinal Disease: Gastroesophageal Reflux Disease (GORD))

Nursing Paper Example on Gastrointestinal Disease: Gastroesophageal Reflux Disease (GORD)

Etiology

Genetic Predisposition: While the exact cause of Gastroesophageal Reflux Disease (GORD) remains multifactorial, genetic predisposition plays a significant role in its development. Studies have identified a familial aggregation of GORD, suggesting a genetic component to the condition. Specific genetic variations may influence the function of the lower esophageal sphincter (LES) or alter gastric motility, predisposing individuals to reflux symptoms.

Obesity: Obesity is a well-established risk factor for GORD, with excess body weight contributing to increased intra-abdominal pressure. This pressure can weaken the LES, allowing gastric contents to reflux into the esophagus more easily. Adipose tissue also produces inflammatory cytokines and hormones that may further disrupt esophageal function and exacerbate reflux symptoms in obese individuals.

Hiatal Hernia: A hiatal hernia occurs when a portion of the stomach protrudes through the diaphragm into the chest cavity, disrupting the normal anatomy of the gastroesophageal junction. This structural abnormality can impair the function of the LES, leading to GORD symptoms. While not all individuals with hiatal hernias develop GORD, the presence of a hiatal hernia increases the risk of reflux and complications.

Smoking: Cigarette smoking is associated with an increased risk of GORD due to its effects on LES function and gastric motility. The chemicals in tobacco smoke can relax the LES, making it more prone to reflux. Smoking also reduces saliva production, which normally helps neutralize stomach acid in the esophagus. Consequently, smokers are more likely to experience severe and prolonged reflux symptoms.

Dietary Factors: Certain dietary habits and food choices can exacerbate GORD symptoms. Spicy, acidic, and fatty foods can irritate the esophagus and stimulate acid production, leading to increased reflux. Common trigger foods include citrus fruits, tomatoes, chocolate, caffeine, and alcohol. Large meals and lying down shortly after eating can also promote acid reflux by increasing intra-abdominal pressure. Identifying and avoiding trigger foods is essential for managing GORD symptoms.

Medications: Several medications are known to exacerbate GORD symptoms or weaken the LES, increasing the risk of reflux. Nonsteroidal anti-inflammatory drugs (NSAIDs) like ibuprofen and aspirin can irritate the esophageal lining and increase acid production, aggravating reflux symptoms. Additionally, calcium channel blockers used to treat hypertension and certain sedatives may relax the LES, facilitating acid reflux.

The etiology of Gastroesophageal Reflux Disease involves a complex interplay of genetic predisposition, obesity, hiatal hernias, smoking, dietary factors, and medications. Understanding these underlying contributors is essential for developing targeted management strategies and addressing modifiable risk factors to alleviate symptoms and improve quality of life. (Nursing Paper Example on Gastrointestinal Disease: Gastroesophageal Reflux Disease (GORD)

Pathophysiology

Lower Esophageal Sphincter Dysfunction: Gastroesophageal Reflux Disease (GORD) primarily involves dysfunction of the lower esophageal sphincter (LES), a muscular ring that acts as a barrier between the esophagus and the stomach. In individuals with GORD, the LES fails to close properly or relaxes inappropriately, allowing gastric contents, including stomach acid and partially digested food, to reflux into the esophagus. This malfunctioning of the LES is central to the pathophysiology of GORD and leads to the characteristic symptoms associated with the condition.

Impaired Esophageal Clearance: Another aspect of GORD’s pathophysiology involves impaired esophageal clearance mechanisms. Normally, the esophagus has efficient mechanisms, including peristalsis and salivary neutralization, to clear refluxed material back into the stomach and neutralize gastric acid. However, in individuals with GORD, these clearance mechanisms may be compromised, leading to prolonged exposure of the esophageal mucosa to acidic gastric contents. This prolonged exposure contributes to esophageal mucosal injury and inflammation, exacerbating symptoms and potentially leading to complications such as erosive esophagitis or Barrett’s esophagus.

Esophageal Mucosal Injury and Inflammation: Repeated exposure of the esophageal mucosa to gastric acid and other corrosive contents leads to mucosal injury and inflammation in individuals with GORD. The acidic nature of gastric contents irritates the esophageal epithelium, causing tissue damage and inflammation. This inflammatory response further compromises esophageal function and exacerbates symptoms such as heartburn, regurgitation, and chest pain. Over time, chronic inflammation may contribute to the development of complications such as esophageal strictures, Barrett’s esophagus, or even esophageal adenocarcinoma in severe cases.

Potential Complications: GORD can lead to various complications due to chronic esophageal mucosal injury and inflammation. These complications may include erosive esophagitis, characterized by erosions or ulcers in the esophageal mucosa, which can cause pain and bleeding. Long-term untreated GORD may also result in the development of Barrett’s esophagus, a condition characterized by changes in the esophageal lining that predispose individuals to esophageal adenocarcinoma, a type of cancer. Additionally, severe and recurrent reflux can lead to esophageal strictures, narrowing of the esophagus that can cause difficulty swallowing and food impaction.

The pathophysiology of Gastroesophageal Reflux Disease involves dysfunction of the lower esophageal sphincter, impaired esophageal clearance mechanisms, mucosal injury, and inflammation. Chronic inflammation and mucosal injury may lead to complications such as erosive esophagitis, Barrett’s esophagus, and esophageal strictures if left untreated. Understanding the underlying pathophysiological mechanisms is essential for the effective management and prevention of complications associated with GORD. (Nursing Paper Example on Gastrointestinal Disease: Gastroesophageal Reflux Disease (GORD)).

Nursing Paper Example on Gastrointestinal Disease: Gastroesophageal Reflux Disease (GORD)

DSM-5 Diagnosis

Clinical Evaluation: Diagnosing Gastroesophageal Reflux Disease (GORD) typically involves a comprehensive clinical evaluation based on the patient’s medical history, symptom presentation, and physical examination. Healthcare providers often rely on the presence of characteristic symptoms such as heartburn, regurgitation, chest pain, and difficulty swallowing to initiate further diagnostic investigations.

Diagnostic Criteria: While the Diagnostic and Statistical Manual of Mental Disorders, Fifth Edition (DSM-5) does not provide specific diagnostic criteria for GORD, it emphasizes the importance of assessing symptom severity and functional impairment in making a diagnosis. Healthcare providers use standardized questionnaires or symptom scales to evaluate the frequency, intensity, and impact of reflux symptoms on the patient’s daily functioning and quality of life.

Objective Measures: In addition to clinical assessment, objective measures such as upper gastrointestinal endoscopy, esophageal pH monitoring, and esophageal manometry may be employed to confirm the diagnosis of GORD and assess the extent of esophageal mucosal injury and dysfunction. Upper gastrointestinal endoscopy allows direct visualization of the esophageal mucosa and the identification of erosions, ulcers, or other pathological changes indicative of GORD. Esophageal pH monitoring measures the frequency and duration of acid reflux episodes, providing valuable information about the severity and pattern of reflux. Esophageal manometry evaluates esophageal motility and LES function, helping to identify underlying motor disorders contributing to GORD symptoms.

Differential Diagnosis: Diagnosing GORD requires differentiation from other conditions that may present with similar symptoms, such as peptic ulcer disease, gastritis, esophageal motility disorders, and cardiac conditions like angina or myocardial infarction. Healthcare providers consider the patient’s medical history, risk factors, symptom pattern, and response to initial interventions to rule out alternative diagnoses and confirm GORD.

Multidisciplinary Approach: Diagnosing GORD often involves a multidisciplinary approach, with collaboration between primary care physicians, gastroenterologists, and other healthcare professionals. This collaborative effort ensures comprehensive evaluation, appropriate diagnostic testing, and tailored management strategies to address individual patient needs and optimize outcomes.

Diagnosing Gastroesophageal Reflux Disease relies on a comprehensive clinical evaluation, standardized symptom assessment, and objective measures to confirm the diagnosis and assess the severity and impact of symptoms. While the DSM-5 does not provide specific diagnostic criteria for GORD, it underscores the importance of evaluating symptom severity and functional impairment in making a diagnosis. Differential diagnosis and a multidisciplinary approach are essential to differentiate GORD from other conditions with similar presentations and ensure optimal management and outcomes for affected individuals. (Nursing Paper Example on Gastrointestinal Disease: Gastroesophageal Reflux Disease (GORD)

Treatment Regimens

Lifestyle Modifications: Effective management of Gastroesophageal Reflux Disease (GORD) often begins with lifestyle modifications aimed at reducing reflux symptoms and improving esophageal health. Patients are advised to avoid trigger foods and beverages known to exacerbate reflux, such as spicy, acidic, and fatty foods, caffeine, alcohol, and carbonated drinks. Additionally, consuming smaller, more frequent meals and avoiding lying down or bending over shortly after eating can help reduce intra-abdominal pressure and minimize reflux episodes.

Weight Management: Obesity is a significant risk factor for GORD, and weight management is an integral component of treatment. Patients are encouraged to achieve and maintain a healthy weight through a balanced diet and regular physical activity. Weight loss can alleviate pressure on the abdomen, reduce reflux symptoms, and improve overall esophageal health.

Elevating the Head of the Bed: Elevating the head of the bed by 6 to 8 inches can help prevent acid reflux during sleep by utilizing gravity to keep stomach contents in the stomach. Patients can achieve this elevation by using bed risers or placing blocks under the bed frame’s legs. Sleeping on a wedge-shaped pillow can also provide similar benefits by elevating the upper body during sleep.

Smoking Cessation: Smoking is a modifiable risk factor for GORD, and smoking cessation is an essential aspect of treatment. Patients are encouraged to quit smoking to reduce LES relaxation, improve esophageal motility, and decrease reflux symptoms. Healthcare providers can offer support and resources to help patients quit smoking, such as counseling, nicotine replacement therapy, or prescription medications.

Medications: Pharmacological interventions are often employed to manage GORD symptoms and reduce esophageal mucosal injury. Proton pump inhibitors (PPIs), such as omeprazole, lansoprazole, and esomeprazole, are commonly prescribed to suppress gastric acid production and promote esophageal healing. H2 receptor antagonists, such as ranitidine and famotidine, can also be used to reduce acid secretion and alleviate reflux symptoms. Antacids may provide symptomatic relief by neutralizing stomach acid, although they are less effective at healing esophageal mucosal damage.

Surgical Intervention: In refractory cases or when complications arise, surgical intervention may be considered to improve LES function and prevent reflux. Fundoplication is a surgical procedure in which the upper part of the stomach is wrapped around the LES to strengthen its closure and reduce reflux. Endoscopic procedures, such as transoral incisionless fundoplication (TIF) or radiofrequency ablation (RFA), may also be performed to tighten the LES and improve reflux control. (Nursing Paper Example on Gastrointestinal Disease: Gastroesophageal Reflux Disease (GORD)

Patient Education: Patient education is essential for empowering individuals to actively participate in their GORD management and achieve optimal outcomes. Patients should be educated about the importance of adhering to lifestyle modifications, including dietary changes, weight management, and smoking cessation, to minimize reflux symptoms and prevent complications. Healthcare providers should discuss the rationale behind recommended interventions, potential side effects of medications, and expected outcomes to enhance patient understanding and adherence.

Monitoring and Follow-Up: Regular monitoring and follow-up are crucial components of GORD management to assess treatment efficacy, adjust interventions as needed, and address any emerging concerns or complications. Patients should be encouraged to report any persistent or worsening symptoms, side effects of medications, or difficulties adhering to recommended lifestyle modifications during follow-up visits.

The management of Gastroesophageal Reflux Disease involves a multifaceted approach encompassing lifestyle modifications, pharmacological interventions, surgical options, and patient education. Tailored treatment regimens should address individual patient needs and preferences while emphasizing the importance of adherence to lifestyle modifications and regular monitoring to achieve optimal symptom control and improve esophageal health.

Conclusion

Gastroesophageal Reflux Disease (GORD) is a complex gastrointestinal disorder with multifactorial etiology and diverse clinical manifestations. This essay has provided an overview of the causes, signs and symptoms, etiology, pathophysiology, DSM-5 diagnosis, treatment regimens, and patient education strategies related to GORD. By emphasizing the importance of simple yet formal language, concise paragraphs, and clear transitions, this essay has sought to enhance readability and comprehension while maintaining a formal tone. Effective management of GORD requires a comprehensive approach that encompasses lifestyle modifications, pharmacological interventions, surgical options, and patient education. By addressing modifiable risk factors, empowering patients through education, and individualizing treatment regimens, healthcare providers can improve symptom control, prevent complications, and enhance the quality of life for individuals living with GORD. (Nursing Paper Example on Gastrointestinal Disease: Gastroesophageal Reflux Disease (GORD).

References

http://Clarrett DM, Hachem C. Gastroesophageal Reflux Disease (GERD). Mo Med. 2018 May-Jun;115(3):214-218. PMID: 30228725; PMCID: PMC6140167.

 
Do you need a similar assignment done for you from scratch? Order now!
Use Discount Code "Newclient" for a 15% Discount!

Computer Science homework help

/in , /by

Database Systems

Introduction to Database Systems

Project Description

This project is based on the material in textbook Chapter 3 – Chapter 5, and Appendix A sections 2 – 5. All the references on figures, chapters/sections

 

The database for Wedgewood Pacific (WP) has been discussed extensively in Chapter 3 as well as in the “Working with Microsoft Access” in Chapter 1 and Chapter 2.

Complete the following four tasks using MySQL (Community Server 8.0 and the Workbench).

Create one document file (Microsoft Word or PDF format) that contains all your SQL scripts (in text format) and clear screenshots (with brief explanation) for all 4 parts.

1. Create the Wedgewood Pacific (WP) database as described in Chapter 3. This will include:

a. Creating the WP schema, and setting it as the default schema.

b. Creating a folder to hold SQL scripts for the WP schema in the C:/Documents/MySQL Workbench/Schemas folder.

c. Creating and running an SQL script named WP-Create-Tables based on Figure 3-7 (page

152) to create the WP table structure.

d. Creating and running an SQL script named WP-Insert-Datas based on Figure 3-11 (pages 159 – 161) to populate the WP tables.

What to turn in?

· Provide screenshots (similar to Figure A-19 and Figure A-20) with a brief explanation to demonstrate that you have completed this task.

 

 

2. Write an SQL query to answer the bolded question below based on the WP database that you have created in part 1.

Who are the employees assigned to projects run by the Sales and Marketing Department? The result should be sorted by ProjectID in ascending order, and contain the following information: ProjectID, ProjectName, Department, DepartmentPhone, EmployeeNumber, LastName, FirstName, and OfficePhone.

What to turn in?

· A copy of your SQL script (in text format, not screenshot image);

· A screenshot of the results of running the query.

 

 

3. Wedgewood Pacific (WP) has decided to keep track of computers used by the employees. To do so, two new tables are added to the database. The schema for these tables, as related to the existing EMPLOYEE table, along with the referential integrity constraints, are shown in question WA.3.3 (pages 241 – 244). In addition, Figure 3-31, Figure 3-32, Figure 3-33, and Figure 3-34 are the corresponding database column characteristics for the tables and table data.

 

The schema for these tables is (note that we are purposely excluding the recursive relationship in EMPLOYEE at this time):

The referential integrity constraints:

 

 

Write an SQL query to answer the following question:

Who is currently using which computer at WP?

The result should be sorted first by Department and then by employee LastName, and contain the following information: SerialNumber, Make, Model, EmployeeID, LastName, FirstName, Department, and OfficePhone.

What to turn in?

· A copy of your SQL script (in text format, not screenshot image);

· A screenshot of the results of running the query.

 

4. Using an IE Crow’s Foot E-R diagram, Figure 5-17 (page 365) and Figure A-67 (page A-73) show the database design for the Wedgewood Pacific database (including the recursive relationship for EMPLOYEE) in MySQL Workbench. See Appendix A section 5 (pages A-56 to A-74) for more details.

Use MySQL Workbench to enhance this E-R diagram (Figure 5-17 or Figure A-67) with the COMPUTER and COMPUTER_ASSIGNMENT tables as mentioned in the previous part.

What to turn in?

· A screenshot of the completed E-R diagram.

 
Do you need a similar assignment done for you from scratch? Order now!
Use Discount Code "Newclient" for a 15% Discount!

Software Architecture And Design

/in , /by

Software Architecture And Design

Trent University COIS 3040H

Assignment #1 Due Feb. 13th, 2015 (submit online by 11:59pm)

1. [20 marks] Consider an automated banking system. Customers access the ABM terminal to deposit or withdraw money or pay bills. TrentMoney wants to set up generic ABMs to cash in on transaction fees. We need to come up with a software architecture that covers the entire system – ABM terminals, Interac, banking servers, and the companies receiving monies for bills. We may not know exactly how the banking servers deal with transactions but we can show the components that they would need and suggest possibilities for communication. Your first step is to identify the components in the system and possible connectors. Then you’ll need to consider the three parts of a software architecture: elements, form, rationale. Then I want you to develop three alternative software architectures for TrentMoney. For each of these provide:

• A description of the architectural style and the rationale for this choice • A description of any architectural patterns chosen and the rationale for these choices • A topological diagram of the system • A deployment diagram of the system

You should submit a professional looking report containing the three alternatives for the software architecture for TrentMoney along with the supporting information. You should also include a recommendation for the architecture that you prefer along with the rationale for your choice. 2. [20 marks] Find 5 examples of software projects that have failed due to faulty design. Describe the reasons for the failure, whether it was caused by an accidental or essential difficulty, and provide solutions for how they could have avoided the failure. 3. [20 marks] Search the Internet for software design tools. Select one of them to write a 1 to 2 pages report on the application of the tool. Your report should including the following:

• Background information – company (URL), motivation of development and purpose of the tool;

• Application – how to use the product (example); • Input/Output and user Interface; • Cost and Product reviews – are there any outside reviews of the product, if so find

them and summarize the review; • Possible references.

 
Do you need a similar assignment done for you from scratch? Order now!
Use Discount Code "Newclient" for a 15% Discount!

Programming assignment

/in , /by

Programming assignment

Again every programming assignment must include the python program and a file with snap-shots of the program running like the case study. You should at least have two files uploaded.

1.         Teachers in most school districts are paid on a schedule that provides a salary based on their number of years of teaching experience. For example, a beginning teacher in the Lexington School District might be paid $30,000 the first year. For each year of experience after this first year, up to 10 years, the teacher receives a 2% increase over the preceding value. Write a program that displays a salary schedule, in tabular format, for teachers in a school district. The inputs are the starting salary, the percentage increase, and the number of years in the schedule. Each row in the schedule should contain the year number and the salary for that year.

 

2.         The credit plan at TidBit Computer Store specifies a 10% down payment and an annual interest rate of 12%. Monthly payments are 5% of the listed purchase price, minus the down payment. Write a program that takes the purchase price as input. The program should display a table, with appropriate headers, of a payment schedule for the lifetime of the loan. Each row of the table should contain the following items:

•           the month number (beginning with 1)

•          the current total balance owed

•           the interest owed for that month

•           the amount of principal owed for that month

•          the payment for that month

•           the balance remaining after payment

The amount of interest for a month is equal to balance * rate / 12. The amount of principal for a month is equal to the monthly payment minus the interest owed.

 

Hints: on formatting tabular data.

# type this in the console of python

for exponent in range(7,11):

print(exponent, 10 ** exponent) #then hit enter two times to see results

# also try print(“%-3d12d” % (exponent, 10  ** exponent))

#Right Justified

“%6s” % “four”

#Left Justified

“%-6s” % “four”

 

#for float %<field wisth>,<presision>f

“%6,3f” % 3.14

#observe the results

 
Do you need a similar assignment done for you from scratch? Order now!
Use Discount Code "Newclient" for a 15% Discount!

Packet Tracker assignment Help 

/in , /by

Packet Tracker assignment Help

Assignment 2: Packet Tracer Task

Top of Form

Hide Assignment Information
Turnitin®
Turnitin® enabledThis assignment will be submitted to Turnitin®.
Instructions
Simulating and Testing Network Configurations

As a network administrator for Bacon Institute, you will need to become familiar with the Packet Tracer simulation tool from Cisco. Packet Tracer is used to simulate and test network configurations. This allows you to work out and improve upon the settings before implementing them.

Using the diagram and configuration information from your first task, create a Packet Tracer simulation.

Submit your .pkt (Packet Tracer) file to the box below.

Review the syllabus for information about late policies and resubmitted assignments.

 

Simulating and Testing Network   Configurations

As a network administrator for   Bacon Institute, you will need to become familiar with the Packet Tracer simulation   tool from Cisco. Packet Tracer is used to simulate and test network   configurations. This allows you to work out and improve upon the settings   before implementing them.

Using the diagram and   configuration information from your first task, create a Packet Tracer   simulation.

Submit your .pkt (Packet Tracer)   file to the box below.

Review the syllabus for   information about late policies and resubmitted assignments.

 
Do you need a similar assignment done for you from scratch? Order now!
Use Discount Code "Newclient" for a 15% Discount!

Using Agile Techniques The Students Will Design A Personal Environment Network.

/in , /by

Using Agile Techniques The Students Will Design A Personal Environment Network.

Project:

Using Agile Techniques the students will design an Personal Environment Network. This will involve each student identifying and classifying which components need addressing and how, using Agile development, this will be achieved. The final outcomes of this will a document or documents addressing these components, (Communication, planning, modeling, construction and deployment).

Organization and Flow:

• Project planning

• Use case development

• Requirement gathering

• Rapid design

• Code generation

• Testing

Area of work:

Using Agile Techniques the students will design an Personal Enviroment Network, This will involve in-class collaboration among the class students as they identify and classify which components need addressing and how, using Agile development, this will be achieved. The final outcomes of this

will a document or documents addressing these components, (Communication, planning, modeling, construction and deployment). The assignment will be further discussed during the lectures including time for students to discuss and work on the project.

Customer Requirements will be discussed in class

Overview:

A personal Environment Network is a network of ad-hoc device (cell phones or other WIFI wireless devices) that organize themselves into an active network to exchange information that is determined by each individual device. The application that allows the information exchange is responsible for security, look and feel and protocol. The underlining communication protocol is also part of the application. Furthermore, the application is capable of routing thru a node to get a link to a node outside a original nodes transmission range. These devices do not need any cell tower requirements, although it is possible.

According to Wikipedia these devices follow this definition:

A mobile ad hoc network (MANET), is a self-configuring infrastructure-less network of mobile devices connected by wireless links. ad hoc is Latin and means “for this purpose”. [1] [2]

Each device in a MANET is free to move independently in any direction, and will therefore change its links to other devices frequently. Each must forward traffic unrelated to its own use, and therefore be a router. The primary challenge in building a MANET is equipping each device to continuously maintain the information required to properly route traffic. Such networks may operate by themselves or may be connected to the larger Internet. MANETs are a kind of wireless ad hoc networks that usually has a routable networking environment on top of a Link Layer ad hoc network.

The growth of laptops and 802.11/Wi-Fi wireless networking have made MANETs a popular research topic since the mid 1990s. Many academic papers evaluate protocols and their abilities, assuming varying degrees of

mobility within a bounded space, usually with all nodes within a few hops of each other.

Different protocols are then evaluated based on measure such as the packet drop rate, the overhead introduced by the routing protocol, end-to-end packet delays, network throughput etc. Use case:

The user of the device sets their device to accept information from:

• Friends

• Ads by category

• Classmates (for example course 680)

• Device specifications in stores

• Home appliance devices

 

Classification of some simple use cases:

1) Item identification and location

2) ad-hoc social networking

3) ad-hoc phone services (vs. cellular phone service)

 
Do you need a similar assignment done for you from scratch? Order now!
Use Discount Code "Newclient" for a 15% Discount!

Assignment Programming

/in , /by

Assignment Programming

CPSC 120 Spring 2014

Lab 9

Practice Objectives of this Lab:

1. Modular Programming

2. Defining and Calling Functions

3. Function Prototypes

4. Sending Data into a Function

5. Passing Data by Value

6. The return Statement

7. Returning a Value from a Function

8. Returning a Boolean Value

9. Using Functions in a Menu-Driven Program

10. Local and Global Variables

11. Arrays as Function Arguments

12. Static Local Variables

13. Using Reference Variables as Parameters

Grading:

1. 9.1 10 points

9.2-9.7 15 points each

100 points totally

2. Your final complete solution report is due at 11:50 PM on Monday, 05/19/2014.

To begin

· Log on to your system and create a folder named Lab9 in your work space.

· Start the C++ IDE (Visual Studio) and create a project named Lab9.

LAB 9.1 – TRY IT: Working with Functions and Function Calls

Step 1: Add the tryIt6A.cpp program in your Lab6 folder to the project. Below is a partial listing of the source code.

1 // Lab 6 tryIt6A

12 /***** main *****/ 13 int main() 14 { int value = 2; 15 16 cout << “Hello from main.\n”; 17 printMessage(); 18 19 cout << “\nValue returned by tripleIt is ” 20 << tripleIt(value) << endl; 21 cout << “In main value now is ” 22 << value << endl << endl; 23 24 value = tripleIt(value); 25 cout << “In main value now is ” 26 << value << endl; 27 28 value = tripleIt(value); 29 cout << “In main value now is ” 30 << value << endl << endl; 31 32 cout << “Goodbye from main.\n”; 33 return 0; 34 } 35 36 /***** printMessage *****/ 37 void printMessage() 38 { 39 cout << “Hello from PrintMessage.\n”; 40 } 41 42 /***** tripleIt *****/ 43 int tripleIt(int someNum) 44 { 45 return someNum * someNum * someNum; 46 }

 Expected Output
  Observed Output

Step 2: Read the source code, paying special attention to the flow of control from main to the functions it calls and then back to main again. Notice what main passes to each function and what, if anything, the function return. Once you have done this, complete the “Expected Output” box in the table above, writing down what the program will display in the order it will be displayed.

Step 3: Now compile and run the tryIt6A.cpp program, and look at the output it creates. If the actual output matches what you wrote down, just place a checkmark in the “Observed Output” box. If it is not the same, write down the actual output.

LAB 9.2 – Using a void Function

Step 1: Remove tryIt6A.cpp from the project and add the fortunes.cpp program in your Lab6 folder to the project. Below is a copy of the source code.

1 // Lab 6 fortunes.cpp 2 // This fortune telling program will be modified to use a void function. 3 // PUT YOUR NAME HERE. 4 #include <iostream> 5 #include <cmath> 6 using namespace std; 7 8 // Function prototype 9 // WRITE A PROTOTYPE FOR THE tellFortune FUNCTION HERE. 10 11 /***** main *****/ 12 int main() 13 { 14 int numYears, 15 numChildren; 16 17 cout << “This program can tell your future. \n” 18 << “Enter two integers separated by a space: “; 19 20 cin >> numYears >> numChildren; 21 22 numYears = abs(numYears) % 5; // Convert to a positive integer 0 to 4 23 numChildren = abs(numChildren) % 6; // Convert to a positive integer 0 to 5 24 25 cout << “\nYou will be married in ” << numYears << ” years ” 26 << “and will have ” << numChildren << ” children.\n”; 27 28 return 0; 29 } 30 31 /***** tellFortune *****/ 32 // WRITE THE tellFortune FUNCTION HEADER HERE.

33 // WRITE THE BODY OF THE tellFortune FUNCTION HERE.

Step 2: Run the program to see how it works. What output do you get when you input the following values at the prompt? -99 14

________________________________________________________________________________

Step 3: Create a function that contains the fortune telling part of the code by doing the following:

· On line 9 write the prototype for a void function named tellFortune that has two integer parameters.

· On line 32 write the function header for the tellFortune function. Following that should be the body of the function. Move lines 22 – 26 of the program to the function body.

· Replace current lines 22 – 26 of main with a call to the tellFortune function that passes it two arguments, numYears and numChildren.

Step 4: Recompile and rerun the program. Enter -99 and 14 again. It should work the same as before.

Step 5: If your professor asks you to do so, print the revised source code and the output of executing it several times, using a variety of inputs.

LAB 9.3 – Modularizing a Program with void Functions

Step 1: Please see a copy of the completed areas2.cpp program and place it in your Lab6 folder. Name it areas3.cpp

// Lab 5 areas2-KEY.cpp

// This menu-driven program finds areas of squares,

// circles, and right triangles.

// It modifies the Lab 4 areas.cpp program to use a do-while loop.

// STUDENT NAME GOES HERE.

#include <iostream>

using namespace std;

int main()

{

const double PI = 3.14159;

double side, // Length of a side of a square

radius, // Radius of a circle

base, // Length of base of a right triangle

height, // Height of a right triangle

area; // Area of a square, circle, or right triangle.

int choice; // User’s menu choice

do

{

// Display the menu

cout << “\n\nProgram to calculate areas of different objects \n\n”;

cout << ” 1 — square \n”

<< ” 2 — circle \n”

<< ” 3 — right triangle \n”

<< ” 4 — quit \n\n”;

cin >> choice;

// Find and display the area of the user’s chosen object

if (choice == 1) // square

{ cout << “Length of the square’s side: “;

cin >> side;

area = side * side;

cout << “Area = ” << area << endl;

}

else if (choice == 2) // circle

{ cout << “Radius of the circle: “;

cin >> radius;

area = PI * radius * radius;

cout << “Area = ” << area << endl;

}

else if (choice == 3) // right triangle

{ cout << “Base of the triangle: “;

cin >> base;

cout << “Height of the triangle: “;

cin >> height;

area = .5 * base * height;

cout << “Area = ” << area << endl;

}

else if (choice != 4)

cout << “Choice must be 1, 2, 3, or 4.\n”;

} while (choice != 4);

return 0;

}

Step 2: Remove fortunes.cpp from the project and add the areas3.cpp program to the project.

Step 3: Modularize the program by adding the following 4 functions. None of them have any parameters.

· void displayMenu()

· void findSquareArea()

· void findCircleArea()

· void findTriangleArea()

To do that you will need to carry out the following steps:

· Write prototypes for the four functions and place them above main.

· Write function definitions (consisting of a function header and initially empty body) for the four functions and place them below main.

· Move the appropriate code out of main and into the body of each function.

· Move variable definitions in main for variables no longer in main to whatever functions now use those variables. They will be local variables in those functions. For example, findSquareArea will need to define the side variable and findCircleArea will need to define the radius variable. All of the functions that compute areas will now need to define a variable named area.

· Move the definition for the named constant PI out of main and place it above the main function.

· In main, replace each block of removed code with a function call to the function now containing that block of code.

Step 4: Compile the code, fixing any errors until it compiles without errors. Then test it. Make sure it runs correctly for all menu choices.

Step 5: If your professor asks you to do so, print the revised source code and the output of executing it , selecting each menu choice at least once.

LAB 9.4 – Using a Function that Returns a Value

Step 1: Remove areas3.cpp from the project and add the choice.cpp program in your Lab6 folder to the project. Below is a copy of the source code.

1 // Lab 6 choice.cpp 2 // This program illustrates how to use a value-returning 3 // function to get, validate, and return input data. 4 // PUT YOUR NAME HERE. 5 #include <iostream> 6 #include <cmath> 7 using namespace std; 8 9 // Function prototype 10 int getChoice(); 11 12 /***** main *****/ 13 int main() 14 { 15 int choice; 16 17 cout << “Enter an integer between 1 and 4: “; 18 19 // WRITE A LINE OF CODE TO CALL THE getChoice FUNCTION AND TO 20 // ASSIGN THE VALUE IT RETURNS TO THE choice VARIABLE. 21 22 cout << “You entered ” << choice << endl; 23 } 24 25 /***** getChoice *****/ 26 int getChoice() 27 { 28 int input; 29 30 // Get and validate the input 31 cin >> input; 32 while (input < 1 || input > 4) 33 { cout << “Invalid input. Enter an integer between 1 and 4: “; 34 cin >> input; 35 } 36 return input; 37 }

Step 2: Read through the code to see how it works. Notice that the getChoice function validates the input before returning it.

Step 3: Follow the directions given in the uppercase comments on lines 4 and 19-20. Then compile and run the program. When prompted for an input, use the data shown in the sample run below. You should get the same results.

Sample Run

Enter an integer between 1 and 4: 0

Invalid input. Enter an integer between 1 and 4: 9

Invalid input. Enter an integer between 1 and 4: 2

You entered 2

Step 4: Now make the getChoice function more versatile so it can validate that a choice is in any desired range, not just 1 – 4. Do this by carrying out the following steps:

· Add two integer parameters named min and max to the function header and modify the function prototype to agree with this.

· Revise the function so that it now validates that the input is between min and max. Remember to change the error prompt as well as the test condition of the while loop.

· Revise the line of code in main that calls the function so that it now passes two arguments to the function. Pass the values 1 and 4 to the function (though other values would work also).

Now recompile and rerun the program, again using the data from the sample run shown above. The program should produce the same results as it did before.

Step 5: If your professor asks you to do so, print the revised source code and the output of executing it with the sample run data.

Lab 9.5 – Modularizing a Program with Value-Returning Functions

For this lab exercise you will make additional improvements to the areas program you worked on in Lab 4, Lab 5, and earlier in this lab.

Step 1: In your Lab6 folder make a copy of your areas3.cpp file. Name it areas4.cpp

Step 2: Remove choice.cpp from the project and add the areas4.cpp program to the project.

Step 3: Copy the getChoice function you just wrote in the choice.cpp file for the Lab 6.4 exercise and paste it below the displayMenu function definition in the areas4.cpp file. Add a function prototype for the getChoice function at the top of the program where the other prototypes are located. Now, change the following line of code in main

cin >> choice;

to

choice = getChoice(1, 4);

This will ensure that choice is assigned a value between 1 and 4. Therefore the final else if can be removed from the if/else if statement that controls the branching. After doing this, test the program to make sure everything works so far, before going on to the next step.

Step 4: Now, make the findSquareArea, findCircleArea, and findTriangleArea functions into value-returning functions. They should each return a double value. Change their function headers and function prototypes to indicate this. Then, instead of having them print the area, have them return the area they have computed. Finally, change the call to each of these functions in main so that the value returned by the function call will be printed. For example, you will change

if (choice == 1)

findSquareArea();

to

if (choice == 1)

cout << “Area = ” << findSquareArea() << endl;

Step 5: Compile the code, fixing any errors until it compiles without errors. Then test it. Make sure it runs correctly for all menu choices.

Step 6: If your professor asks you to do so, print the revised source code and the output of executing it , selecting each menu choice at least once.

Lab 9.6 – Using Value and Reference Parameters

Step 1: Remove areas4.cpp from the project and add the swapNums.cpp program in your Lab6 folder to the project. Below is a copy of the source code.

1 // Lab 6 swapNums.cpp — Using Value and Reference Parameters 2 // This program uses a function to swap the values in two variables. 3 // PUT YOUR NAME HERE. 4 #include <iostream> 5 using namespace std; 6 7 // Function prototype 8 void swapNums(int, int); 9 10 /***** main *****/ 11 int main() 12 { 13 int num1 = 5, 14 num2 = 7; 15 16 // Print the two variable values 17 cout << “In main the two numbers are ” 18 << num1 << ” and ” << num2 << endl; 19 20 // Call a function to swap the values stored 21 // in the two variables 22 swapNums(num1, num2); 23 24 // Print the same two variable values again 25 cout << “Back in main again the two numbers are ” 26 << num1 << ” and ” << num2 << endl; 27 28 return 0; 29 } 30 31 /***** swapNums *****/ 32 void swapNums(int a, int b) 33 { // Parameter a receives num1 and parameter b receives num2 34 // Swap the values that came into parameters a and b 35 int temp = a; 36 a = b; 37 b = temp; 38 39 // Print the swapped values 40 cout << “In swapNums, after swapping, the two numbers are ” 41 << a << ” and ” << b << endl; 42 }

Step 2: Read the source code, paying special attention to the swapNums parameters. When the program is run do you think it will correctly swap the two numbers? Compile and run the program to find out.

Explain what happened. _________________________________________________________________

______________________________________________________________________________________

______________________________________________________________________________________

Step 3: Change the two swapNums parameters to be reference variables. Section 6.13 of your text shows how to do this. You will need to make the change on both the function header and the function prototype. Nothing will need to change in the function call. After making this change, recompile and rerun the program. If you have done this correctly, you should get the following output.

In main the two numbers are 5 and 7

In swapNums, after swapping, the two numbers are 7 and 5

Back in main again the two numbers are 7 and 5

Explain what happened this time. _________________________________________________________

______________________________________________________________________________________

______________________________________________________________________________________

You do not need to hand in the source code or output from this lab exercise.

Lab 9.7 – Complete Program

Step 1: Remove swapNums.cpp from the project and add the kiloConverter.cpp program in your Lab6 folder to the project. This file contains just a program shell in which you will write the programming statements needed to complete the program described below. Here is a copy of the file.

1 // Lab 6 kiloConverter.cpp 2 // This menu-driven program lets the user convert 3 // pounds to kilograms and kilograms to pounds. 4 // PUT YOUR NAME HERE. 5 #include <iostream> 6 using namespace std; 7 8 // Function prototypes 9 // WRITE PROTOTYPES FOR THE displayMenu, getChoice, 10 // kilosToPounds and poundsToKilos FUNCTIONS HERE. 11 12 /***** main *****/ 13 int main() 14 { 15 // DECLARE ANY VARIABLES MAIN USES HERE. 16 17 // WRITE THE CODE HERE TO CARRY OUT THE STEPS 18 // REQUIRED BY THE PROGRAM SPECIFICATIONS. 19 20 return 0; 21 } 22 23 /***** displayMenu *****/ 24 // WRITE THE displayMenu FUNCTION HERE. 25 // THIS void FUNCTION DISPLAYS THE MENU CHOICES 26 // 1. Convert kilograms to pounds 27 // 2. Convert pounds to kilograms 28 // 3. Quit 29 30 /***** getChoice *****/ 31 // THIS IS THE SAME FUNCTION YOU WROTE EARLIER IN THIS SET 32 // OF LAB EXERCISES. JUST FIND IT AND PASTE IT HERE. 33 34 /***** kilosToPounds *****/ 35 // WRITE THE kilosToPounds FUNCTION HERE. 36 // IT RECEIVES A WEIGHT IN KILOS AND MUST CALCULATE 37 // AND RETURN THE EQUIVALENT NUMBER OF POUNDS. 38 39 /***** poundsToKilos *****/ 40 // WRITE THE poundsToKilos FUNCTION HERE. 41 // IT RECEIVES A WEIGHT IN POUNDS AND MUST CALCULATE 42 // AND RETURN THE EQUIVALENT NUMBER OF KILOS.

Step 2: Design and implement a modular, menu-driven program that converts kilograms to pounds and pounds to kilograms. 1 kilogram = 2.2 pounds. The program should display a menu, accept and validate a user menu choice, get the amount of weight to be converted, call the appropriate function to do the conversion, and then print the returned result. The code should continue iterating to allow additional conversions to be done until the user enters the menu choice to quit. When the program runs it should look somewhat like the sample run shown here.

Sample Run

1. Convert kilograms to pounds

2. Convert pounds to kilograms

3. Quit

1

Weight to be converted: 4

4 kilograms = 8.8 pounds.

1. Convert kilograms to pounds

2. Convert pounds to kilograms

3. Quit

2

Weight to be converted: 10

10 pounds = 4.54545 kilograms.

1. Convert kilograms to pounds

2. Convert pounds to kilograms

3. Quit

3

Step 3: Once your program is written and compiles with no errors, thoroughly test it.

Step 4: If your professor asks you to do so, print the completed source code and the output produced by executing it , selecting each menu choice at least once.

2

 
Do you need a similar assignment done for you from scratch? Order now!
Use Discount Code "Newclient" for a 15% Discount!