Reputation
1,621
Next privilege 2,000 Rep.
Edit questions and answers
Badges
5 6
Newest
 Yearling
Impact
~58k people reached

  • 0 posts edited
  • 0 helpful flags
  • 24 votes cast
Jul
27
comment How to work with programmer with different preference of indentation width?
there is no such thing as "everyone agrees". that concept breaks immediately when the group of people increases in size. the concept doesnt scale to larger teams -> not a good solution.
Jul
23
revised C++ design for encoder/decoder classes with different stored types
added 38 characters in body
Jul
23
revised C++ design for encoder/decoder classes with different stored types
added 1 character in body
Jul
23
revised C++ design for encoder/decoder classes with different stored types
added 5 characters in body
Jul
23
revised C++ design for encoder/decoder classes with different stored types
deleted 2 characters in body
Jul
23
revised C++ design for encoder/decoder classes with different stored types
added 4 characters in body
Jul
23
revised C++ design for encoder/decoder classes with different stored types
added 110 characters in body
Jul
23
revised C++ design for encoder/decoder classes with different stored types
added 82 characters in body
Jul
23
answered C++ design for encoder/decoder classes with different stored types
Jul
23
revised C++ design for encoder/decoder classes with different stored types
added 66 characters in body
Jul
23
revised C++ design for encoder/decoder classes with different stored types
added 261 characters in body
Jul
23
revised C++ design for encoder/decoder classes with different stored types
added 340 characters in body
Jul
23
answered C++ design for encoder/decoder classes with different stored types
Jul
14
comment Why are datatypes different in terms of bit size based on complier, and OS used
compilers need freedom to match your source code and the underlying CPU architecture while generating the code. Different CPU architectures work slightly different way, but your C++ source code still needs to work in all of them. Consider sizeof(T) to be documentation of how your compiler code generation handles types.
Jul
14
answered What design pattern best suits managing handles to objects, without passing handles or Manager around?
Jun
27
answered Functional programming and Text adventures
May
27
revised Taking strong, static typing to an extreme?
added 262 characters in body
May
27
answered Taking strong, static typing to an extreme?
May
27
comment Taking strong, static typing to an extreme?
@gallais: yes, but the trick in haskell would be to use Maybe type with the nothing-branch, instead of asserts terminating the program. The logic will still be part of the runtime program, instead of just comments. Just the checking is not being done by the compiler.
May
26
comment Taking strong, static typing to an extreme?
haskell already have this feature implemented. It cannot check it on compile-time, or even on runtime, but the rule basically is as follows: "before you create instance of a type with constructor, you must check invariant of the type." If you follow this rule, you'll never get prime type with non-prime instances, even though the internal data structure is described by ints.