Delphi programming course questions, answered plainly

No. A course teaches the language in a planned order, while Arraydeck works on the units you already have: it reads them, explains them, proposes edits as diffs and runs your build command. Many learners use both. Follow the lessons, then ask the agent to explain a handler from your own project, and check every answer against your compiler. Use whichever order of the two suits your own pace.

Object Pascal is the language behind Delphi. It uses begin ... end blocks, strings in single quotes, := for assignment and = for comparison, and a function returns its value through Result. Units are split into an interface section and an implementation section. Arraydeck reads and edits this code as text, and you compile and test it yourself with your own build command.

A unit is a .pas source file with 2 sections: the interface section lists what other units can use, and the implementation section holds the code. A uses clause names the other units it needs. One file, two sections. Arraydeck opens units with read_file, finds them with glob and grep, and proposes every edit as a diff that you accept or reject. The file you open is plain text.

No. RAD is not no code, because every event handler, such as a button click, is still Object Pascal that you write and maintain. Visual design helps you lay out a form, not the logic behind it. Arraydeck helps with the code part: it reads a handler, explains it and edits it as a diff you review. Visual layout is quick; logic needs thought.

Legacy Delphi code archeology is the careful reading of an old project before any change. List the .pas and .dpr files, find where the main program starts and follow the uses clauses from unit to unit. Arraydeck helps with list_dir, glob, grep and read_file, and it writes nothing until you ask for an edit and accept the diff. Start small and read each file in full.

Yes, this is the official Arraydeck website. Download the setup program here and compare its SHA-256 checksum with the published manifest before you run it on your PC. The installer is not code-signed yet, so Windows SmartScreen may warn you. Questions? Press the Send feedback button inside the app and describe what you saw. Pick the version for Windows 10 or 11.

No. Arraydeck edits source files as text, and it cannot promise that code compiles, passes your tests or does what you meant. You read every diff, run your own build command and test the result. Ask first pauses before actions that change something, so a wrong answer costs you reading time and not a broken unit. Your tests are the judge here.

No, not as a one-click conversion. Arraydeck can read a unit, explain what it does and write draft files into the working folder, one diff at a time. A port to another language is a long job that you must review and test yourself, and the agent cannot promise that the new code builds or behaves like the old one. Draft files are only a starting point.

Ask first is the mode to start with. It pauses before actions that change something and shows the diff to accept or reject, so you see each edit before it touches a file. Auto-run acts at once, and Plan only writes a plan and runs nothing, which suits a first look at a large project. You can switch modes at any time.

Yes, in two ways. It can search your project with grep for the units that already use WebSockets and explain what they do, and web_search and http_get can read documentation pages for the details. It cannot test a live connection for you. You accept the code, build it and test it on your own machine. The agent does not run a server for you.

Three kinds: a cloud AI provider through a standard API endpoint, a model running locally on your PC, and the built-in model, which is ready to use without an endpoint of your own. Press the Test button to see the response time and the context window. Choose a bigger model for refactors and a smaller one for small edits. Switch models whenever a task needs it.

No, not with a local model. With a cloud AI provider, the prompt, including text from files the agent reads, goes to that provider and falls under that provider's own terms. With a model running locally on your PC, nothing leaves the machine. Chats, working folders and API keys stay on the PC either way. The app sends no telemetry. Cloud billing is between you and the provider.

The importance of code signing for Windows apps is that it lets Windows show who published a file. The Arraydeck installer is not code-signed yet, so Windows SmartScreen may warn you. Compare the SHA-256 checksum of the download with the published manifest, and only then choose More info and Run anyway, once the values match. A checksum match is the real signal.

The app sends prompts only to the model endpoint you pick. Optional features use the network too: web search, which can run over an anonymizing network, control of chats from a phone browser through one outbound connection that you can switch off, and update checks. With a local model and those features off, nothing leaves the PC. Each of those can be switched off or avoided.