 Swapping two variables does not depend on the type is an integral part of the language. And has always been in 1983 that was not that common, but you have a whole system and task is really easy to use. You don't hesitate to put tasks in your program. So this is something I want to stress. We have seen that the compiler is doing the mapping from the high level to the low level. Sometimes you have requirements at the low level. Therefore you can specify the exact low level representation. Here I have a record. I can specify that what the Boolean called on is inward zero and its range of bit zero to zero. So it's one bit that counts these range one to seven and so on. So you specify the high level, you specify the low level. And the idea that once you've done that, you continue to work at a high level. If you want to set a bit, you write, because it's an array of bits, mi.status of three, column equal false, high level. And you get an end with the correct mask at the low level. So for people who say, oh, I need to do bit fiddling, therefore I need a low level language, the answer is no. You specify the low level and still the compiler is still mapping the high level to the low level. You continue to work at a high level and get what you want at a low level. Okay, really low level, it's easy to access memory. We have packages that allow you to write directly in memory. That's not a problem. You can include machine code. You can handle interrupt. All these features are provided. But the question is, if it's low level, it must be stated clearly. Because these features are provided by packages, you must name the package on top of your unit. And therefore, the reader of your program will know that this is accessing low level. Okay? We don't want some dirty tricks under the carpet. I mentioned the special needs annex. Here are the topics, system programming, real time, distributed system, information system, numerics, and safety and security annex. Now named high reliability annex. So it's really portable and there are checks. There is a validation suite to make sure that compilers implement exactly the same language. And believe me, I sometimes write code on my laptop in the tram on a window system. I then copy that to Linux and I don't even check on Linux. If it works on one system, it does the same thing on the other. So the free compiler is called that. It has excellent error messages, but I have few time left. So I have to hurry a little bit. Many components and Ada is one of them. I don't think there are many languages who took care to define how to interface with other languages. Both ways. You can call other languages from Ada and Ada can be called from other languages. This means that every available library that you are used to can also be used in Ada. So conclusion almost in time. You think that I would tell you, oh, use Ada. No, I won't tell you that because I think you are grownups and you are free to do whatever you want. Now, I would simply advise you to try it. Give it a try. See what it means to have that higher level view where the compiler frees you from all low level details and protects you. And believe me, when you start having that help from the compiler, it's hard to return to lower level languages. That's it. Do we have time for questions? Yes? It's important now how the door is open. Well, synchronization is another issue. Okay. Many attempts, for example, to define atomic variables, also synchronization mechanisms, height and barriers and so on. This is being discussed for the next version of the language. I missed the end of the end because there was just someone asking something. Thank you for the talk. It raised more questions and answers for me and that's always where... Oh, that's why you are for. Thank you for the first intention and I have some questions. Just before all of you leave, there is some literature that you can pick up on the table offered by Ada Kor. So there is not much, but if you want you can... There is a booklet like Ada for the C++ programmer. Okay. Can I... Sure. It's possible? No problem. Thank you for the presentation. I wanted to... For me, Ada, it's been a very long time that I wanted to try. I tried a lot of languages, etc. Do you have a list of 5-10 projects that we can do, but which are rather focused on Ada? I'm going to try languages on Akeur Anke, but to do algos around strings, etc. It's really not... Yes, no, it's not funny. To learn... There is already something that is good to learn, it's Rosetta Code. Yes, it's part of things, but do you have projects that are more focused on... utility, I don't know, of Ada? Let's say that I do a lot of training on Ada. So... I have exercises, but... a mini-project of the level of... a mini-project, I don't have a specific idea like that, or... For example, an exercise that we do quite regularly, when we do functional language, is to write a computer, because it works quite well. We have an AST to manipulate, an art of mathematical transformation for Ada. Here we have a very powerful tool called ASIS, that is to say that it's an API that allows you to access the entire tree of the Ada program. Basically, the compiler crashes into a file, its tree is decorated, and we have an API that allows you to go through it. So... I write utilitarian things like that, but we write it completely in the AST, it's very pleasant, it's called ASIS, but it's not very... I wouldn't advise it for beginners. And things that are more oriented, that are embedded or things... So... Do you know the BBC Card? It's a small card, it forms a credit card that embarks a weapon, things, it's worth... 15 euros, I think. And... okay, provide a development environment for this thing. Okay. So... It's like the chain... They did that for the... for the pedagogical courses of the BBC in informatics. Okay, okay. So it's really so that the kids can know... that for Jean-Paul. And... Can you read it? So, Fabia Suto agrees. And... I wanted to talk about the BBC Card. Yes, of course. So... Because they're looking for small projects to play a bit with the language. We have a blog. A blog? Okay, okay. We have a lot of small projects. Okay, okay, great.