Some construct that is almost identical between Java and C++ (eg. loop statement, condition statement) may not be discussed in this document.
#include <iostream>
int main(int argc, char** args) {
#include <iostream> | |
#include <array> | |
#include <chrono> | |
#include <string> | |
#include <ctime> | |
#include <cstdlib> | |
class timer { | |
private: | |
const std::chrono::system_clock::time_point start; |
#include <iostream> | |
#include <ft2build.h> | |
#include FT_FREETYPE_H | |
#include FT_OUTLINE_H | |
#include <SDL2/SDL.h> | |
#include <SDL2/SDL_main.h> | |
#include <string> |
#include <iostream> | |
#include <SDL.h> | |
#include <SDL_mixer.h> | |
#include <vorbis/vorbisfile.h> | |
using namespace std; | |
int main(int, char **) { | |
SDL_Init(SDL_INIT_EVERYTHING); | |
atexit(SDL_Quit); | |
Mix_Init(MIX_INIT_FLAC | MIX_INIT_OGG); |
/************************************************************************** | |
* AlStream : Play streaming OGG file with custom loop points. | |
* License : Public Domain. | |
* Usage: alStream input.ogg | |
* | |
* Note: | |
* | |
* The input file will be played infintely until the program close. If the | |
* input file has the `loop_end` comment in its header, the file will be played | |
* to that point then loop back to start. If the input file has the `loop_start` |
#include <iostream> | |
#include <codecvt> | |
#include <iomanip> | |
#include <SDL2/SDL.h> | |
#include <ft2build.h> | |
#include FT_FREETYPE_H | |
constexpr char teststring[] {"Hello World"}; |
using System; | |
using System.Collections.Generic; | |
using System.ComponentModel; | |
using System.Data; | |
using System.Drawing; | |
using System.Linq; | |
using System.Text; | |
using System.Threading.Tasks; | |
using System.Windows.Forms; | |
using SkiaSharp; |
import 'bootstrap/dist/css/bootstrap.css' | |
import 'bootstrap-vue/dist/bootstrap-vue.css' | |
// JS import | |
import Vue from 'vue'; | |
import App from './App.vue' | |
import BootstrapVue from 'bootstrap-vue' | |
Vue.use(BootstrapVue); |
Most application, services, app, program, whatever has some kind of configurations. Some of the them are visible to the user, some of them are only available to the provider, some of them might be derived from other settings.
In larger applications, like web services and stuffs, configurations play a huge role. No one wants to recompile the whole program when there are needs to move the log file location, for example. Well-implemented applications provides numbers of configuration, so they are flexible enough to handle different environments and usages.
Below is what I think it should be taken in consideration when designing configuration management.
There are multiple way to keep and to read the configuration. It could be an in-memory objects, SQLite, SQL server, No-SQL server, Redis, or even a configuration server. Regardless, this should be considered as a 'detail'. The application should not aware of how these operations work. It should be able to query t