4 ms·

I suspect sometimes that StephanTLavavej is way too productive to be just one person. Maybe a pseudonym under which the whole MSVC compiler / stl team operates

by dman 11y ago

I suspect sometimes that StephanTLavavej is way too productive to be just one person. Maybe a pseudonym under which the whole MSVC compiler / stl team operates (much like https://en.wikipedia.org/?title=Nicolas_Bourbaki https://en.wikipedia.org/?title=Nicolas_Bourbaki ) :) Thanks for being great at outreach.

minot 11y ago
If there is more than one STL, here is one who claims to be him https://channel9.msdn.com/Series/C9-Lectures-Stephan-T-Lavavej-Core-C-/Stephan-T-Lavavej-Core-C-1-of-n https://channel9.msdn.com/Series/C9-Lectures-Stephan-T-Lavav... http://nuwen.net/stl.html http://nuwen.net/stl.html
StephanTLavavej 11y ago
Heh! Nobody's ever called me a collective entity before. I just happen to enjoy writing and keeping track of these feature tables, which is why I publish them. My real work goes into STL features and fixes, which is just one part of a very large product that many other compiler and library devs work on.
zerr 11y ago
To be fair, and I always thought it quite interesting - Microsoft's STL (C++ Standard Library) is the work of a single person company Dinkumware run by P. J. Plauger. https://en.wikipedia.org/wiki/P._J._Plauger#Dinkumware https://en.wikipedia.org/wiki/P._J._Plauger#Dinkumware
- stinos 11y ago
  Is that still the case? Is there no real 'stl team' at MS and everything is written by Dinkumware? Or is there a more entwined collaboration between them?
  - StephanTLavavej 11y ago
    It's entwined, and has been for nearly a decade. MS licensed Dinkumware's STL back in the mid-90s (and I know almost nothing about the early history). Around 2005, MS was doing things like adding security features to the STL, but not really sustained development. In Jan 2007, I joined the VC team and since then I've spent almost all of my time on the STL (with one brief detour). For a long time, I fixed bugs, dealt with MS-specific stuff (DLLs, calling conventions), reported compiler bugs, that sort of stuff, with PJP delivering new features (starting with TR1 in 2008 SP1). I review all STL checkins, preventing bugs from happening in the first place. In the last few years, I've tackled larger overhauls and started implementing larger features. For example, in this release I rewrote the TR1-era <functional> implementation (keeping only std::function's skeleton), implementing C++17 invoke() as a side effect. Other MS devs have contributed STL bugfixes in this release, and a couple of features (e.g. uncaught_exceptions() and sized deallocation), so it's not just the PJP and STL show.

by dman 11y ago

minot 11y ago

If there is more than one STL, here is one who claims to be him https://channel9.msdn.com/Series/C9-Lectures-Stephan-T-Lavavej-Core-C-/Stephan-T-Lavavej-Core-C-1-of-n https://channel9.msdn.com/Series/C9-Lectures-Stephan-T-Lavav... http://nuwen.net/stl.html http://nuwen.net/stl.html

StephanTLavavej 11y ago

Heh! Nobody's ever called me a collective entity before. I just happen to enjoy writing and keeping track of these feature tables, which is why I publish them. My real work goes into STL features and fixes, which is just one part of a very large product that many other compiler and library devs work on.

zerr 11y ago

To be fair, and I always thought it quite interesting - Microsoft's STL (C++ Standard Library) is the work of a single person company Dinkumware run by P. J. Plauger. https://en.wikipedia.org/wiki/P._J._Plauger#Dinkumware https://en.wikipedia.org/wiki/P._J._Plauger#Dinkumware

stinos 11y ago
Is that still the case? Is there no real 'stl team' at MS and everything is written by Dinkumware? Or is there a more entwined collaboration between them?
- StephanTLavavej 11y ago
  It's entwined, and has been for nearly a decade. MS licensed Dinkumware's STL back in the mid-90s (and I know almost nothing about the early history). Around 2005, MS was doing things like adding security features to the STL, but not really sustained development. In Jan 2007, I joined the VC team and since then I've spent almost all of my time on the STL (with one brief detour). For a long time, I fixed bugs, dealt with MS-specific stuff (DLLs, calling conventions), reported compiler bugs, that sort of stuff, with PJP delivering new features (starting with TR1 in 2008 SP1). I review all STL checkins, preventing bugs from happening in the first place. In the last few years, I've tackled larger overhauls and started implementing larger features. For example, in this release I rewrote the TR1-era <functional> implementation (keeping only std::function's skeleton), implementing C++17 invoke() as a side effect. Other MS devs have contributed STL bugfixes in this release, and a couple of features (e.g. uncaught_exceptions() and sized deallocation), so it's not just the PJP and STL show.