![]() ![]() Below a basic (incomplete) example of a GET request with a custom header, but as this is just a binding to libcurl, it basically allows you to do anything, including other protocols (libcurl can even have SMTP support, depending how it is compiled). No need to install anything on Lazarus/FPC. on Windows you need to install the DLL, e.g. As the LLDB integration is all new, it needs a lot of testing. So there should no longer be a need to build and codesign gdb. It is based on LLDB, which is provided by apple and is ready to use. works perfectly fine (tested on Windows and Linux, I suppose MacOS will work too. With the Lazarus Release Candidate 1 for 2.0 a new debugger for Mac users has been shipped. Those days I'm using libcurl with the bindings that are supplied with Lazarus/FPC. And all the new methods use 0-based indices for strings. But now they added OOP like string functions and it became weirder. With Lazarus you can easily create native applications and deploy them to many platforms. It is already weird, but you can get used to it. Lazarus IDE is a powerful and free open source cross platform rapid application development environment. You can have classes with ARC which are almost memory safe, but only if you use an interface.Īrray indices start with 0, string indices start with 1. Except, in Pascal they are also COM interfaces and add automated reference counting to a class. Everyone here knows how they work and in Pascal they work in the same way. They specify some methods, but not their implementation. ![]() Interfaces are a very common concept in OOP languages. Also it looks like it cannot be used with a slice of length 0, unless it is a slice of an array of length 0. There is a type to store a slice of an array, but it can only be used during function calls, so no one ever uses it. There is a type to store sets of integers, but you cannot have more than 256 elements There is mutability xor aliasing, but only for strings There is automated reference counting to get memory safety, but only for strings and arrays (and also interfaces but we get to that later) It is twice as weird in FreePascal, because the developers cannot decide if they want to make their own language or be Delphi compatible. They always implement some language feature, but then put some weird, arbitrary restriction on it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |