![]() ![]() In addition, the cost of virtual-method call indirection and object-dereferencing could result in very significant performance & scale penalties for C++ code at that time. Even today, the hidden costs of code written in C++ can be surprising, but back in the late 1990’s, when memory cost ~$60/MB (yes … $60 per MEGABYTE!), the hidden memory cost of vtables etc. Why? C++ introduces a cost in terms of memory footprint, and code execution overhead. ![]() The answer is that – despite NT’s Object-Based design – like most OS’, Windows is almost entirely written in ‘C’. Windows Console is a traditional Win32 executable and, though it was originally written in ‘C’, much of the code is being migrated to modern C++ as the team modernizes and modularizes Console’s codebase.įor those who care about such things: Many have asked whether Windows is written in C or C++. However, the Windows Console does things a little differently: Inside the Windows Console Terminate when required, or when the communications channel is closed/terminated.output text, move the cursor, set text color, etc.) Update the display as required, based on the received app output (e.g.Accept text output from a connected Command-Line app/tool.Send characters to the connected app/tool/shell.Translate input into relevant characters and/or ANSI/VT sequences.Accept input from devices including keyboard, mouse, touch, pen, etc.The Windows Console code-base is currently (July 2018) almost 30 years old … older, in fact, than the developers who now work on it! □ What does the Console do?Īs we learned in our previous posts, a Terminal’s job is relatively simple: Windows Console is one of the first Windows NT GUI apps, and is certainly one of the oldest Windows apps still in general use. When the Windows GUI’s implementation started to arrive, the team needed a Console GUI app and thus, the Windows Console was born. Introducing the Windows Pseudo Console (ConPTY)ĭuring the initial development of Windows NT, circa 1989, there was no GUI, there was no desktop, there was ONLY a full-screen command-line, that visually resembled MS-DOS more than it did the future.The Evolution of the Windows Command-Line.Note: This chapter list will be updated as more posts are published: Posts in the “Windows Command-Line” series ![]() In this post, we’ll start to dig into the internals of the Windows Console and Command-Line, what it is, what it does … and what it doesn’t do. Welcome to the third post in the Windows Command-Line series. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |