testsuite/tests/python/analysis_parse_buffer/test.py

import libadalang


src_buffer = b"""
limited with Ada.Text_IO;

procedure Foo is
   function \"+\" (S : String) return String is (S);
begin
   Ada.Text_IO.Put_Line (+\"Hello, world!\");
end Foo;
"""

ctx = libadalang.AnalysisContext('iso-8859-1')
unit = ctx.get_from_buffer('foo.adb', src_buffer)
assert unit, 'Could not create the analysis unit for foo.adb from a buffer'

print('Done.')
Rework the analysis API Revamp the analysis context primitives to create/remove analysis units so that: * their behavior is defined in error cases * reparsing is possible * parsing from a memory buffer is possible Update existing testcases to cope with these changes and add new ones to exercise these features in the C and Python APIs. Followup on O519-029 Change-Id: I409d63bef32cb1a920f402d7957ba8cd2668eb66 2015-05-20 12:56:39 +02:00			`import libadalang`

Enforce two empty lines after imports TN: S819-013 2019-08-19 13:43:46 +02:00
Add Python3 compatibility for the Python bindings TN: SB13-026 2019-11-28 11:31:37 +01:00			`src_buffer = b"""`
Rework the analysis API Revamp the analysis context primitives to create/remove analysis units so that: * their behavior is defined in error cases * reparsing is possible * parsing from a memory buffer is possible Update existing testcases to cope with these changes and add new ones to exercise these features in the C and Python APIs. Followup on O519-029 Change-Id: I409d63bef32cb1a920f402d7957ba8cd2668eb66 2015-05-20 12:56:39 +02:00			`limited with Ada.Text_IO;`

			`procedure Foo is`
			`function \"+\" (S : String) return String is (S);`
			`begin`
			`Ada.Text_IO.Put_Line (+\"Hello, world!\");`
			`end Foo;`
			`"""`

Add charset selection to public APIs and update Ada material This change makes it possible for the users of Langkit-generated libraries to select the charset to use to decode input sources. As a consequence, it also updates the Ada testsuite to the new APIs and introduce a couple of testcases to check that charset handling is done properly. There are still two things left to do in order to have the Unicode support in Langkit done API-wise: * detect early when the provided charset is not supported and raise a well-specified error in this case; * specify what happens when the input is badly encoded (for instance when decoding ISO-8859-1 sources as UTF-8 ones) and implement it: currently the Quex lexer just calls exit(), which is not acceptable. Change-Id: Ifc76427143ffcec9fe56832b16d1372eaf0463c9 TN: O414-018 2015-10-19 18:22:07 -04:00			`ctx = libadalang.AnalysisContext('iso-8859-1')`
Rework the analysis API Revamp the analysis context primitives to create/remove analysis units so that: * their behavior is defined in error cases * reparsing is possible * parsing from a memory buffer is possible Update existing testcases to cope with these changes and add new ones to exercise these features in the C and Python APIs. Followup on O519-029 Change-Id: I409d63bef32cb1a920f402d7957ba8cd2668eb66 2015-05-20 12:56:39 +02:00			`unit = ctx.get_from_buffer('foo.adb', src_buffer)`
			`assert unit, 'Could not create the analysis unit for foo.adb from a buffer'`

tests/: update __future__ imports TN: Q223-029 2017-02-24 11:13:34 +01:00			`print('Done.')`