Mercurial > vim
view runtime/doc/ft_ada.txt @ 32936:c517845bd10e v9.0.1776
patch 9.0.1776: No support for stable Python 3 ABI
Commit: https://github.com/vim/vim/commit/c13b3d1350b60b94fe87f0761ea31c0e7fb6ebf3
Author: Yee Cheng Chin <ychin.git@gmail.com>
Date: Sun Aug 20 21:18:38 2023 +0200
patch 9.0.1776: No support for stable Python 3 ABI
Problem: No support for stable Python 3 ABI
Solution: Support Python 3 stable ABI
Commits:
1) Support Python 3 stable ABI to allow mixed version interoperatbility
Vim currently supports embedding Python for use with plugins, and the
"dynamic" linking option allows the user to specify a locally installed
version of Python by setting `pythonthreedll`. However, one caveat is
that the Python 3 libs are not binary compatible across minor versions,
and mixing versions can potentially be dangerous (e.g. let's say Vim was
linked against the Python 3.10 SDK, but the user sets `pythonthreedll`
to a 3.11 lib). Usually, nothing bad happens, but in theory this could
lead to crashes, memory corruption, and other unpredictable behaviors.
It's also difficult for the user to tell something is wrong because Vim
has no way of reporting what Python 3 version Vim was linked with.
For Vim installed via a package manager, this usually isn't an issue
because all the dependencies would already be figured out. For prebuilt
Vim binaries like MacVim (my motivation for working on this), AppImage,
and Win32 installer this could potentially be an issue as usually a
single binary is distributed. This is more tricky when a new Python
version is released, as there's a chicken-and-egg issue with deciding
what Python version to build against and hard to keep in sync when a new
Python version just drops and we have a mix of users of different Python
versions, and a user just blindly upgrading to a new Python could lead to
bad interactions with Vim.
Python 3 does have a solution for this problem: stable ABI / limited API
(see https://docs.python.org/3/c-api/stable.html). The C SDK limits the
API to a set of functions that are promised to be stable across
versions. This pull request adds an ifdef config that allows us to turn
it on when building Vim. Vim binaries built with this option should be
safe to freely link with any Python 3 libraies without having the
constraint of having to use the same minor version.
Note: Python 2 has no such concept and this doesn't change how Python 2
integration works (not that there is going to be a new version of Python
2 that would cause compatibility issues in the future anyway).
---
Technical details:
======
The stable ABI can be accessed when we compile with the Python 3 limited
API (by defining `Py_LIMITED_API`). The Python 3 code (in `if_python3.c`
and `if_py_both.h`) would now handle this and switch to limited API
mode. Without it set, Vim will still use the full API as before so this
is an opt-in change.
The main difference is that `PyType_Object` is now an opaque struct that
we can't directly create "static types" out of, and we have to create
type objects as "heap types" instead. This is because the struct is not
stable and changes from version to version (e.g. 3.8 added a
`tp_vectorcall` field to it). I had to change all the types to be
allocated on the heap instead with just a pointer to them.
Other functions are also simply missing in limited API, or they are
introduced too late (e.g. `PyUnicode_AsUTF8AndSize` in 3.10) to it that
we need some other ways to do the same thing, so I had to abstract a few
things into macros, and sometimes re-implement functions like
`PyObject_NEW`.
One caveat is that in limited API, `OutputType` (used for replacing
`sys.stdout`) no longer inherits from `PyStdPrinter_Type` which I don't
think has any real issue other than minor differences in how they
convert to a string and missing a couple functions like `mode()` and
`fileno()`.
Also fixed an existing bug where `tp_basicsize` was set incorrectly for
`BufferObject`, `TabListObject, `WinListObject`.
Technically, there could be a small performance drop, there is a little
more indirection with accessing type objects, and some APIs like
`PyUnicode_AsUTF8AndSize` are missing, but in practice I didn't see any
difference, and any well-written Python plugin should try to avoid
excessing callbacks to the `vim` module in Python anyway.
I only tested limited API mode down to Python 3.7, which seemes to
compile and work fine. I haven't tried earlier Python versions.
2) Fix PyIter_Check on older Python vers / type##Ptr unused warning
For PyIter_Check, older versions exposed them as either macros (used in
full API), or a function (for use in limited API). A previous change
exposed PyIter_Check to the dynamic build because Python just moved it
to function-only in 3.10 anyway. Because of that, just make sure we
always grab the function in dynamic builds in earlier versions since
that's what Python eventually did anyway.
3) Move Py_LIMITED_API define to configure script
Can now use --with-python-stable-abi flag to customize what stable ABI
version to target. Can also use an env var to do so as well.
4) Show +python/dyn-stable in :version, and allow has() feature query
Not sure if the "/dyn-stable" suffix would break things, or whether we
should do it another way. Or just don't show it in version and rely on
has() feature checking.
5) Documentation first draft. Still need to implement v:python3_version
6) Fix PyIter_Check build breaks when compiling against Python 3.8
7) Add CI coverage stable ABI on Linux/Windows / make configurable on Windows
This adds configurable options for Windows make files (both MinGW and
MSVC). CI will also now exercise both traditional full API and stable
ABI for Linux and Windows in the matrix for coverage.
Also added a "dynamic" option to Linux matrix as a drive-by change to
make other scripting languages like Ruby / Perl testable under both
static and dynamic builds.
8) Fix inaccuracy in Windows docs
Python's own docs are confusing but you don't actually want to use
`python3.dll` for the dynamic linkage.
9) Add generated autoconf file
10) Add v:python3_version support
This variable indicates the version of Python3 that Vim was built
against (PY_VERSION_HEX), and will be useful to check whether the Python
library you are loading in dynamically actually fits it. When built with
stable ABI, it will be the limited ABI version instead
(`Py_LIMITED_API`), which indicates the minimum version of Python 3 the
user should have, rather than the exact match. When stable ABI is used,
we won't be exposing PY_VERSION_HEX in this var because it just doesn't
seem necessary to do so (the whole point of stable ABI is the promise
that it will work across versions), and I don't want to confuse the user
with too many variables.
Also, cleaned up some documentation, and added help tags.
11) Fix Python 3.7 compat issues
Fix a couple issues when using limited API < 3.8
- Crash on exit: In Python 3.7, if a heap-allocated type is destroyed
before all instances are, it would cause a crash later. This happens
when we destroyed `OptionsType` before calling `Py_Finalize` when
using the limited API. To make it worse, later versions changed the
semantics and now each instance has a strong reference to its own type
and the recommendation has changed to have each instance de-ref its
own type and have its type in GC traversal. To avoid dealing with
these cross-version variations, we just don't free the heap type. They
are static types in non-limited-API anyway and are designed to last
through the entirety of the app, and we also don't restart the Python
runtime and therefore do not need it to have absolutely 0 leaks.
See:
- https://docs.python.org/3/whatsnew/3.8.html#changes-in-the-c-api
- https://docs.python.org/3/whatsnew/3.9.html#changes-in-the-c-api
- PyIter_Check: This function is not provided in limited APIs older than
3.8. Previously I was trying to mock it out using manual
PyType_GetSlot() but it was brittle and also does not actually work
properly for static types (it will generate a Python error). Just
return false. It does mean using limited API < 3.8 is not recommended
as you lose the functionality to handle iterators, but from playing
with plugins I couldn't find it to be an issue.
- Fix loading of PyIter_Check so it will be done when limited API < 3.8.
Otherwise loading a 3.7 Python lib will fail even if limited API was
specified to use it.
12) Make sure to only load `PyUnicode_AsUTF8AndSize` in needed in limited API
We don't use this function unless limited API >= 3.10, but we were
loading it regardless. Usually it's ok in Unix-like systems where Python
just has a single lib that we load from, but in Windows where there is a
separate python3.dll this would not work as the symbol would not have
been exposed in this more limited DLL file. This makes it much clearer
under what condition is this function needed.
closes: #12032
Signed-off-by: Christian Brabandt <cb@256bit.org>
Co-authored-by: Yee Cheng Chin <ychin.git@gmail.com>
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Sun, 20 Aug 2023 21:30:04 +0200 |
parents | f8116058ca76 |
children | 4635e43f2c6f |
line wrap: on
line source
*ft_ada.txt* For Vim version 9.0. Last change: 2022 Mar 13 ADA FILE TYPE PLUG-INS REFERENCE MANUAL~ ADA *ada.vim* 1. Syntax Highlighting |ft-ada-syntax| 2. File type Plug-in |ft-ada-plugin| 3. Omni Completion |ft-ada-omni| 3.1 Omni Completion with "gnat xref" |gnat-xref| 3.2 Omni Completion with "ctags" |ada-ctags| 4. Compiler Support |ada-compiler| 4.1 GNAT |compiler-gnat| 4.2 Dec Ada |compiler-decada| 5. References |ada-reference| 5.1 Options |ft-ada-options| 5.2 Commands |ft-ada-commands| 5.3 Variables |ft-ada-variables| 5.4 Constants |ft-ada-constants| 5.5 Functions |ft-ada-functions| 6. Extra Plug-ins |ada-extra-plugins| ============================================================================== 1. Syntax Highlighting ~ *ft-ada-syntax* This mode is designed for the 2005 edition of Ada ("Ada 2005"), which includes support for objected-programming, protected types, and so on. It handles code written for the original Ada language ("Ada83", "Ada87", "Ada95") as well, though code which uses Ada 2005-only keywords will be wrongly colored (such code should be fixed anyway). For more information about Ada, see http://www.adapower.com. The Ada mode handles a number of situations cleanly. For example, it knows that the "-" in "-5" is a number, but the same character in "A-5" is an operator. Normally, a "with" or "use" clause referencing another compilation unit is coloured the same way as C's "#include" is coloured. If you have "Conditional" or "Repeat" groups coloured differently, then "end if" and "end loop" will be coloured as part of those respective groups. You can set these to different colours using vim's "highlight" command (e.g., to change how loops are displayed, enter the command ":hi Repeat" followed by the colour specification; on simple terminals the colour specification ctermfg=White often shows well). There are several options you can select in this Ada mode. See |ft-ada-options| for a complete list. To enable them, assign a value to the option. For example, to turn one on: > > let g:ada_standard_types = 1 > To disable them use ":unlet". Example: > > unlet g:ada_standard_types You can just use ":" and type these into the command line to set these temporarily before loading an Ada file. You can make these option settings permanent by adding the "let" command(s), without a colon, to your "~/.vimrc" file. Even on a slow (90Mhz) PC this mode works quickly, but if you find the performance unacceptable, turn on |g:ada_withuse_ordinary|. Syntax folding instructions (|fold-syntax|) are added when |g:ada_folding| is set. ============================================================================== 2. File type Plug-in ~ *ft-ada-indent* *ft-ada-plugin* The Ada plug-in provides support for: - auto indenting (|indent.txt|) - insert completion (|i_CTRL-N|) - user completion (|i_CTRL-X_CTRL-U|) - tag searches (|tagsrch.txt|) - Quick Fix (|quickfix.txt|) - backspace handling (|'backspace'|) - comment handling (|'comments'|, |'commentstring'|) The plug-in only activates the features of the Ada mode whenever an Ada file is opened and adds Ada related entries to the main and pop-up menu. ============================================================================== 3. Omni Completion ~ *ft-ada-omni* The Ada omni-completions (|i_CTRL-X_CTRL-O|) uses tags database created either by "gnat xref -v" or the "Universal Ctags" (https://ctags.io). The complete function will automatically detect which tool was used to create the tags file. ------------------------------------------------------------------------------ 3.1 Omni Completion with "gnat xref" ~ *gnat-xref* GNAT XREF uses the compiler internal information (ali-files) to produce the tags file. This has the advantage to be 100% correct and the option of deep nested analysis. However the code must compile, the generator is quite slow and the created tags file contains only the basic Ctags information for each entry - not enough for some of the more advanced Vim code browser plug-ins. NOTE: "gnat xref -v" is very tricky to use as it has almost no diagnostic output - If nothing is printed then usually the parameters are wrong. Here some important tips: 1) You need to compile your code first and use the "-aO" option to point to your .ali files. 2) "gnat xref -v ../Include/adacl.ads" won't work - use the "gnat xref -v -aI../Include adacl.ads" instead. 3) "gnat xref -v -aI../Include *.ad?" won't work - use "cd ../Include" and then "gnat xref -v *.ad?" 4) Project manager support is completely broken - don't even try "gnat xref -Padacl.gpr". 5) Vim is faster when the tags file is sorted - use "sort --unique --ignore-case --output=tags tags" . 6) Remember to insert "!_TAG_FILE_SORTED 2 %sort ui" as first line to mark the file assorted. ------------------------------------------------------------------------------ 3.2 Omni Completion with "ctags"~ *ada-ctags* Universal/Exuberant Ctags use their own multi-language code parser. The parser is quite fast, produces a lot of extra information and can run on files which currently do not compile. There are also lots of other Vim-tools which use Universal/Exuberant Ctags. Universal Ctags is preferred, Exuberant Ctags is no longer being developed. You will need to install Universal Ctags which is available from https://ctags.io The Ada parser for Universal/Exuberant Ctags is fairly new - don't expect complete support yet. ============================================================================== 4. Compiler Support ~ *ada-compiler* The Ada mode supports more than one Ada compiler and will automatically load the compiler set in |g:ada_default_compiler| whenever an Ada source is opened. The provided compiler plug-ins are split into the actual compiler plug-in and a collection of support functions and variables. This allows the easy development of specialized compiler plug-ins fine tuned to your development environment. ------------------------------------------------------------------------------ 4.1 GNAT ~ *compiler-gnat* GNAT is the only free (beer and speech) Ada compiler available. There are several versions available which differ in the licence terms used. The GNAT compiler plug-in will perform a compile on pressing <F7> and then immediately shows the result. You can set the project file to be used by setting: > > call g:gnat.Set_Project_File ('my_project.gpr') Setting a project file will also create a Vim session (|views-sessions|) so - like with the GPS - opened files, window positions etc. will be remembered separately for all projects. *gnat_members* GNAT OBJECT ~ *g:gnat.Make()* g:gnat.Make() Calls |g:gnat.Make_Command| and displays the result inside a |quickfix| window. *g:gnat.Pretty()* g:gnat.Pretty() Calls |g:gnat.Pretty_Program| *g:gnat.Find()* g:gnat.Find() Calls |g:gnat.Find_Program| *g:gnat.Tags()* g:gnat.Tags() Calls |g:gnat.Tags_Command| *g:gnat.Set_Project_File()* g:gnat.Set_Project_File([{file}]) Set gnat project file and load associated session. An open project will be closed and the session written. If called without file name the file selector opens for selection of a project file. If called with an empty string then the project and associated session are closed. *g:gnat.Project_File* g:gnat.Project_File string Current project file. *g:gnat.Make_Command* g:gnat.Make_Command string External command used for |g:gnat.Make()| (|'makeprg'|). *g:gnat.Pretty_Program* g:gnat.Pretty_Program string External command used for |g:gnat.Pretty()| *g:gnat.Find_Program* g:gnat.Find_Program string External command used for |g:gnat.Find()| *g:gnat.Tags_Command* g:gnat.Tags_Command string External command used for |g:gnat.Tags()| *g:gnat.Error_Format* g:gnat.Error_Format string Error format (|'errorformat'|) ------------------------------------------------------------------------------ 4.2 Dec Ada ~ *compiler-hpada* *compiler-decada* *compiler-vaxada* *compiler-compaqada* Dec Ada (also known by - in chronological order - VAX Ada, Dec Ada, Compaq Ada and HP Ada) is a fairly dated Ada 83 compiler. Support is basic: <F7> will compile the current unit. The Dec Ada compiler expects the package name and not the file name to be passed as a parameter. The compiler plug-in supports the usual file name convention to convert the file into a unit name. Both '-' and '__' are allowed as separators. *decada_members* DEC ADA OBJECT ~ *g:decada.Make()* g:decada.Make() function Calls |g:decada.Make_Command| and displays the result inside a |quickfix| window. *g:decada.Unit_Name()* g:decada.Unit_Name() function Get the Unit name for the current file. *g:decada.Make_Command* g:decada.Make_Command string External command used for |g:decada.Make()| (|'makeprg'|). *g:decada.Error_Format* g:decada.Error_Format string Error format (|'errorformat'|). ============================================================================== 5. References ~ *ada-reference* ------------------------------------------------------------------------------ 5.1 Options ~ *ft-ada-options* *g:ada_standard_types* g:ada_standard_types bool (true when exists) Highlight types in package Standard (e.g., "Float"). *g:ada_space_errors* *g:ada_no_trail_space_error* *g:ada_no_tab_space_error* *g:ada_all_tab_usage* g:ada_space_errors bool (true when exists) Highlight extraneous errors in spaces ... g:ada_no_trail_space_error - but ignore trailing spaces at the end of a line g:ada_no_tab_space_error - but ignore tabs after spaces g:ada_all_tab_usage - highlight all tab use *g:ada_line_errors* g:ada_line_errors bool (true when exists) Highlight lines which are too long. Note: This highlighting option is quite CPU intensive. *g:ada_rainbow_color* g:ada_rainbow_color bool (true when exists) Use rainbow colours for '(' and ')'. You need the rainbow_parenthesis for this to work. *g:ada_folding* g:ada_folding set ('sigpft') Use folding for Ada sources. 's': activate syntax folding on load 'p': fold packages 'f': fold functions and procedures 't': fold types 'c': fold conditionals 'g': activate gnat pretty print folding on load 'i': lone 'is' folded with line above 'b': lone 'begin' folded with line above 'p': lone 'private' folded with line above 'x': lone 'exception' folded with line above 'i': activate indent folding on load Note: Syntax folding is in an early (unusable) stage and indent or gnat pretty folding is suggested. For gnat pretty folding to work the following settings are suggested: -cl3 -M79 -c2 -c3 -c4 -A1 -A2 -A3 -A4 -A5 For indent folding to work the following settings are suggested: shiftwidth=3 softtabstop=3 *g:ada_abbrev* g:ada_abbrev bool (true when exists) Add some abbreviations. This feature is more or less superseded by the various completion methods. *g:ada_withuse_ordinary* g:ada_withuse_ordinary bool (true when exists) Show "with" and "use" as ordinary keywords (when used to reference other compilation units they're normally highlighted specially). *g:ada_begin_preproc* g:ada_begin_preproc bool (true when exists) Show all begin-like keywords using the colouring of C preprocessor commands. *g:ada_omni_with_keywords* g:ada_omni_with_keywords Add Keywords, Pragmas, Attributes to omni-completions (|compl-omni|). Note: You can always complete then with user completion (|i_CTRL-X_CTRL-U|). *g:ada_extended_tagging* g:ada_extended_tagging enum ('jump', 'list') use extended tagging, two options are available 'jump': use tjump to jump. 'list': add tags quick fix list. Normal tagging does not support function or operator overloading as these features are not available in C and tagging was originally developed for C. *g:ada_extended_completion* g:ada_extended_completion Uses extended completion for <C-N> and <C-R> completions (|i_CTRL-N|). In this mode the '.' is used as part of the identifier so that 'Object.Method' or 'Package.Procedure' are completed together. *g:ada_gnat_extensions* g:ada_gnat_extensions bool (true when exists) Support GNAT extensions. *g:ada_with_gnat_project_files* g:ada_with_gnat_project_files bool (true when exists) Add gnat project file keywords and Attributes. *g:ada_default_compiler* g:ada_default_compiler string set default compiler. Currently supported are 'gnat' and 'decada'. An "exists" type is a boolean considered true when the variable is defined and false when the variable is undefined. The value to which the variable is set makes no difference. ------------------------------------------------------------------------------ 5.2 Commands ~ *ft-ada-commands* :AdaRainbow *:AdaRainbow* Toggles rainbow colour (|g:ada_rainbow_color|) mode for '(' and ')'. :AdaLines *:AdaLines* Toggles line error (|g:ada_line_errors|) display. :AdaSpaces *:AdaSpaces* Toggles space error (|g:ada_space_errors|) display. :AdaTagDir *:AdaTagDir* Creates tags file for the directory of the current file. :AdaTagFile *:AdaTagFile* Creates tags file for the current file. :AdaTypes *:AdaTypes* Toggles standard types (|g:ada_standard_types|) colour. :GnatFind *:GnatFind* Calls |g:gnat.Find()| :GnatPretty *:GnatPretty* Calls |g:gnat.Pretty()| :GnatTags *:GnatTags* Calls |g:gnat.Tags()| ------------------------------------------------------------------------------ 5.3 Variables ~ *ft-ada-variables* *g:gnat* g:gnat object Control object which manages GNAT compiles. The object is created when the first Ada source code is loaded provided that |g:ada_default_compiler| is set to 'gnat'. See |gnat_members| for details. *g:decada* g:decada object Control object which manages Dec Ada compiles. The object is created when the first Ada source code is loaded provided that |g:ada_default_compiler| is set to 'decada'. See |decada_members| for details. ------------------------------------------------------------------------------ 5.4 Constants ~ *ft-ada-constants* All constants are locked. See |:lockvar| for details. *g:ada#WordRegex* g:ada#WordRegex string Regular expression to search for Ada words. *g:ada#DotWordRegex* g:ada#DotWordRegex string Regular expression to search for Ada words separated by dots. *g:ada#Comment* g:ada#Comment string Regular expression to search for Ada comments. *g:ada#Keywords* g:ada#Keywords list of dictionaries List of keywords, attributes etc. pp. in the format used by omni completion. See |complete-items| for details. *g:ada#Ctags_Kinds* g:ada#Ctags_Kinds dictionary of lists Dictionary of the various kinds of items which the Ada support for Ctags generates. ------------------------------------------------------------------------------ 5.5 Functions ~ *ft-ada-functions* ada#Word([{line}, {col}]) *ada#Word()* Return full name of Ada entity under the cursor (or at given line/column), stripping white space/newlines as necessary. ada#List_Tag([{line}, {col}]) *ada#Listtags()* List all occurrences of the Ada entity under the cursor (or at given line/column) inside the quick-fix window. ada#Jump_Tag ({ident}, {mode}) *ada#Jump_Tag()* List all occurrences of the Ada entity under the cursor (or at given line/column) in the tag jump list. Mode can either be 'tjump' or 'stjump'. ada#Create_Tags ({option}) *ada#Create_Tags()* Creates tag file using Ctags. The option can either be 'file' for the current file, 'dir' for the directory of the current file or a file name. gnat#Insert_Tags_Header() *gnat#Insert_Tags_Header()* Adds the tag file header (!_TAG_) information to the current file which are missing from the GNAT XREF output. ada#Switch_Syntax_Option ({option}) *ada#Switch_Syntax_Option()* Toggles highlighting options on or off. Used for the Ada menu. *gnat#New()* gnat#New () Create a new gnat object. See |g:gnat| for details. ============================================================================== 6. Extra Plugins ~ *ada-extra-plugins* You can optionally install the following extra plug-ins. They work well with Ada and enhance the ability of the Ada mode: backup.vim http://www.vim.org/scripts/script.php?script_id=1537 Keeps as many backups as you like so you don't have to. rainbow_parenthsis.vim http://www.vim.org/scripts/script.php?script_id=1561 Very helpful since Ada uses only '(' and ')'. nerd_comments.vim http://www.vim.org/scripts/script.php?script_id=1218 Excellent commenting and uncommenting support for almost any programming language. matchit.vim http://www.vim.org/scripts/script.php?script_id=39 '%' jumping for any language. The normal '%' jump only works for '{}' style languages. The Ada mode will set the needed search patterns. taglist.vim http://www.vim.org/scripts/script.php?script_id=273 Source code explorer sidebar. There is a patch for Ada available. The GNU Ada Project distribution (http://gnuada.sourceforge.net) of Vim contains all of the above. ============================================================================== vim: textwidth=78 nowrap tabstop=8 shiftwidth=4 softtabstop=4 noexpandtab vim: filetype=help