#Uses of putty software portable#
#Uses of putty software code#

We use -Wvla when building with gcc and clang, to make it easier to avoid accidentally breaking that rule.įor historical reasons, we still build with one older VS version which lacks. Visual Studio doesn't support them even now that it's adopted the rest of C99. The exceptions to that rule are due to the need for Visual Studio compatibility:ĭon't use variable-length arrays.

With a couple of exceptions, you can assume that C99 features are available (in particular, and inline), but you shouldn't use things that are new in C11 (such as or _Generic). Our current choice of C standards version is mostly C99. The Windows front end compiles on both 32- and 64-bit x86 and also Arm.) (Even within a platform front end you should still be careful of some of these portability issues. This also means you should stick to the C semantics guaranteed by the C standard: try not to make assumptions about the precise size of basic types such as int and long int don't use pointer casts to do endianness-dependent operations, and so on.

#Uses of putty software code#

The Unix-specific modules are all in the unix subdirectory the Windows-specific modules are in the windows subdirectory.Īll the modules in the main source directory and other subdirectories - notably all of the code for the various back ends - are platform-generic. The PuTTY source base is divided into platform-specific modules and platform-generic modules.

#Uses of putty software portable#

Adding large amounts of Windows-specific stuff in parts of the code that should be portable is almost guaranteed to make us reject a contribution. We went to great lengths to remove all the Windows-specific stuff from our core modules, and to shift it out into Windows-specific modules. Therefore, embedding Windows-specific code in core modules such as ssh.c is not acceptable. It has a working Unix port a Mac port is in progress more ports may or may not happen at a later date. If you are planning to send code contributions, you should read this first.ĭespite Windows being its main area of fame, PuTTY is no longer a Windows-only application suite.

This appendix lists a selection of the design principles applying to the PuTTY source code.

E.12 Explicit vtable structures to implement traits.

E.10 640×480 friendliness in configuration panels.

E.9 Keystrokes sent to the server wherever possible.

E.3 Multiple sessions per process on some platforms.