~/.aqlrc is just another aql script that can be loaded automatically
when the aql shell starts.

You can put standard aql commands inside the file.

Load the standard library files into Prompt.
The iteration order of the file list is unspecified[1] but I don't think
we have to deal with it anyhow. Even we create two files, say a.aql, and
b.aql and a function in b.aql uses a function from a.aql, the loading
order doesn't matter anyway.

Let's start working on a standard library [1]. The idea is that we
bundle some aql files with predefined functions (and procedures) and we
load them when aql prompt starts.

So let's prepare a configuration file with a location for the scripts.
The location is currently only in local dev tree. We will later change
that to some /usr/share or /usr/lib location.

[1] #221

even though here the constant is not magical at all, it makes sense to have auto
here to let the array of escaped and actual special characters easily
extensible. Should that ever be needed.

Jan Trávníček authored 3 years ago and Jan Trávníček committed 3 years ago

breaking change!

the completion function gets int start and int end representing
boundaries of the completed text. The value is provided offset so there
should not be any need for negative values and I believe we may promote
that by internaly treating the values as unsigneds everywhere.

... because most developers were copy-pasting the preambule anyway and
did not pay any attention to change it.

Also, I think that git does better job in managing that.

Tomáš Pecka authored 4 years ago and Jan Trávníček committed 4 years ago

Although #pragma once is not a standard, compilers nowadays usually
support it. We don't have any tricky build system so we should be OK.

This also fixes many errors regarding using reserved identifiers (names
starting with double underscore).

Simplify versioning by CMake. Uses git version in the format
"<major>.<minor>.<patch>.r<commits-since-version-tag>.g<hash>(-dirty)?".