On Thu, Feb 14, 2008 at 11:02 PM, Micha Nelissen <[EMAIL PROTECTED]> wrote:
> ik wrote:
> > Hi,
> >
> > I found that the Do_Syscalls are written in assembly and have only
> > limited number of parameters (up to 6). Is there a way to write it
> > using array of TSysParam instead of having 7 dif
Along Joost's examples I managed to get connected, create a table, put a
query, get the result, and insert a single row. But when I try to insert
several rows at once, I get an EDatabaseError "near" to first char of
second row.
...
q.SQL.Clear;
q.Add('insert into MYTABLE(c1, c2, ..) values ');
q.A
> > Another question is, is there a way to use it witthout writing
> > assembly, like using it in libc or some other way ?
>
> Calling them doesn't require assembler, or what do you mean? You can try
> to extend the compiler to support inlining of assembly functions ;-).
Or custom calling conven
ik wrote:
> Hi,
>
> I found that the Do_Syscalls are written in assembly and have only
> limited number of parameters (up to 6). Is there a way to write it
> using array of TSysParam instead of having 7 different functions ?
Maybe but it wouldn't make the assembler easier to read :-).
> Another
Marco van de Voort schrieb:
>> On 14 Feb 2008, at 07:15, Skybuck Flying wrote:
>>
>>> Here is my idea for a compiler application programming interface
>>> (api) / specification:
>> The comphook unit in combination with the compiler unit already
>> provides such an api. It is used by the text mo
> On 14 Feb 2008, at 07:15, Skybuck Flying wrote:
>
> > Here is my idea for a compiler application programming interface
> > (api) / specification:
>
> The comphook unit in combination with the compiler unit already
> provides such an api. It is used by the text more IDE.
The comphook unit u
On 14 Feb 2008, at 07:15, Skybuck Flying wrote:
Here is my idea for a compiler application programming interface
(api) / specification:
The comphook unit in combination with the compiler unit already
provides such an api. It is used by the text more IDE.
Jonas
__
> Is it doable ?
If you don't want to set any parameters ( in other words no compiler options
dialogue)
> I might try and implement a little dll myself in Delphi by simply using the
> fpc.exe and parsing it's output.
>
> Somebody with advanced knowledge of the compiler sources, might be able
Hello,
Here is my idea for a compiler application programming interface (api) /
specification:
type
// informs which file was tried by compiler, if successfull error text
should be nil, else it should contain some kind of error messages
TcompilerFileTriedCallback = procedure( FullFilename : P
