Am 05.05.2017 21:19 schrieb "Mark Morgan Lloyd" <
markmll.fpc-pas...@telemetry.co.uk>:
>
> On 04/05/17 22:30, Sven Barth via fpc-pascal wrote:
>>
>> Hello together!
>> Since revision 36105 FPC now supports the use of array constructorsusing
the "[...]" syntax inside ordinary code blocks like
In our previous episode, Brian said:
> Affinity
>
> If a thread is dedicated to say , polling a serial or Ethernet port which
> has a high input data rate , then dedicating one CPU to that task/thread is
> useful.
Well, the driver actually does the hardware, so it is already buffered for
Affinity
If a thread is dedicated to say , polling a serial or Ethernet port which
has a high input data rate , then dedicating one CPU to that task/thread is
useful.
(Hard Affinity) with multi-core CPU's is to dedicate a specific core to a
task (thread) and just poll the input memory mapped
On 04/05/17 22:30, Sven Barth via fpc-pascal wrote:
Hello together!
Since revision 36105 FPC now supports the use of array constructorsusing the
"[...]" syntax inside ordinary code blocks like Delphi doessince - I think -
XE8. And yes, even nested ones are supported (take alook at
On 2017-05-05 14:25, Michael Van Canneyt wrote:
> But it's somewhat confusing, because the second patch modifies the first.
Thanks Michael. I guess it took two attempts to fix the issue at hand. If
that was me, I would probably have flattened the changes to a single commit.
$ git merge
On Fri, 5 May 2017, Graeme Geldenhuys wrote:
Hi,
I received notification of a patch (pull request) via my FPC Git mirror.
The author has been notified to rather use Mantis, but seems to have some
troubles registering.
If anybody with FPC commit access wanted to take a look, the patch can be
Hi,
I received notification of a patch (pull request) via my FPC Git mirror.
The author has been notified to rather use Mantis, but seems to have some
troubles registering.
If anybody with FPC commit access wanted to take a look, the patch can be
found here.
On 04/05/17 20:30, Mark Morgan Lloyd wrote:
The record that Dialedit generates to represent initial or extracted
dialogue box values has alignment and/or packing problems. There's a
comment in the source that the FreeVision sources expect dwords while
the author using a debugger believed that
Hi,
probably related also to https://bugs.freepascal.org/view.php?id=30764
(but this my report is mostly about pointer parameters where NO
DIRECTION is specified)
-Laco.
Hello,
I wanted to import the UIAutomationClient type library. Thus I
compiled the UIAutomationClient.idl to .tlb and then
