On 16/08/17 15:45, Benito van der Zander wrote:
> Hi,
[sorry I could not stop myself from reordering your top-post]
> Am 16.08.2017 um 15:48 schrieb Gabor Boros:
>> 2017. 08. 16. 15:21 keltezéssel, Michael Van Canneyt írta:
>>> Because the quotes must be the first and last character of each
>>> s
A bit of news which I think has some interest here:
"Kattis" (open.kattis.com) is a site where students can make programming
exercises. This is quite important IMHO; companies look at Kattis
results when recruiting.
Recently, Kattis added Pascal support, using FPC 3.0.0! (Free Pascal
versio
Hi,
Maybe I'm going blind (considering the amount of screen time its very
likely), but I don't see any link to the Free Pascal Foundation from the
Free Pascal homepage?
https://www.freepascal.org/
Why is that? Surely the two should be related.
On a side note:
Also, why isn't there a "D
On Thu, 17 Aug 2017, Graeme Geldenhuys wrote:
Hi,
Maybe I'm going blind (considering the amount of screen time its very
likely), but I don't see any link to the Free Pascal Foundation from the
Free Pascal homepage?
https://www.freepascal.org/
Why is that? Surely the two should be rela
Hi,
If somebody with more experience (than me) with the Synaser and FPC
serial.pp units could comment, that would be much appreciated.
For a new cross-platform project where I need to talk to a device hooked
up to a serial port, which unit would be the best to use? Normally I
would go with u
On 2017-08-16 18:14, Sven Barth via fpc-pascal wrote:
As you can see the program will work correctly as long as the
libX11.so.6 file exists (even though that is a symlink itself, but the
X11 project guarantees that different libX11.so.6.x.y are compatible to
eachother), because the linker picks t
Am 17.08.2017 15:49 schrieb "Graeme Geldenhuys" <
mailingli...@geldenhuys.co.uk>:
>
> On 2017-08-16 18:14, Sven Barth via fpc-pascal wrote:
>>
>> As you can see the program will work correctly as long as the
>> libX11.so.6 file exists (even though that is a symlink itself, but the
>> X11 project gu
On Thursday 17 August 2017 17:31:46 Sven Barth via fpc-pascal wrote:
> Am 17.08.2017 15:49 schrieb "Graeme Geldenhuys" <
>
> mailingli...@geldenhuys.co.uk>:
> > On 2017-08-16 18:14, Sven Barth via fpc-pascal wrote:
> >> As you can see the program will work correctly as long as the
> >> libX11.so.6
Dne 17.08.2017 v 15:45 Graeme Geldenhuys napsal(a):
>
> Now for the Synaser unit - the one I have is from 2013, and I already
> noticed that there is no support for FreeBSD's /dev/* names to access
> serial ports. Granted I added FreeBSD support to the
> GetSerialPortNames() function in 5 minut
On 2017-08-17 18:05, gebylist wrote:
For most actual Synaser version you must look at Synapse SVN server.;-)
Synaser have class TBlockSerial. It can work with*any* device name. (It
know to emulate Windows COMxx names on Linux too.)
Thank you Lukas, I'll make sure to get the latest from SVN a
On 2017-08-17 16:52, Martin Schreiber wrote:
Exactly. So why not use the SONAME in the Pascal binding unit instead to use
the base name as Free Pascal currently does in xlib.pp for example?
I forked the xlib, xutils and x units from FPC and tried just that. It
made no difference. When I compil
On 17 Aug 2017 21:21, "Graeme Geldenhuys"
wrote:
On 2017-08-17 16:52, Martin Schreiber wrote:
> Exactly. So why not use the SONAME in the Pascal binding unit instead to
> use
> the base name as Free Pascal currently does in xlib.pp for example?
>
I forked the xlib, xutils and x units from FPC a
In our previous episode, Martin Schreiber said:
> > nevertheless be failures if the applications
> > is programmed against the interface of the older v1 library (maybe they
> > changed the memory management for v2 and the problem will only manifest at
> > runtime).
> >
> Exactly. So why not use the
Am 17.08.2017 22:20 schrieb "Graeme Geldenhuys" <
mailingli...@geldenhuys.co.uk>:
>
> On 2017-08-17 16:52, Martin Schreiber wrote:
>>
>> Exactly. So why not use the SONAME in the Pascal binding unit instead to
use
>> the base name as Free Pascal currently does in xlib.pp for example?
>
>
> I forked
On 2017-08-17 21:47, Henry Vermaak wrote:
You can use -l:libgreat.so.1 with gcc to link to a specific library version
(iirc).
I'll have to take your word for it Henry, as I don't know GCC much -
only the bare minimum to compile small C projects. I normally specify
things like -lpthreads -lX11
On 2017-08-17 22:17, Marco van de Voort wrote:
if some distribution halfway through the release cycle starts packaging a
new version.
But surely then the program would be broken anyway - in the case of a
major version number bump. It is well known that major version changes
mean two versions
The results may be sorted also by language name and so all C++ results
comes in before Pascal even if runtime is the same. Your program was as
fast as No1 but anyway not visible among top ten. This outrageous! ;-)
On 08/17/2017 10:21 AM, Ingemar Ragnemalm wrote:
A bit of news which I think h
On Thursday 17 August 2017 22:20:44 Graeme Geldenhuys wrote:
> On 2017-08-17 16:52, Martin Schreiber wrote:
> > Exactly. So why not use the SONAME in the Pascal binding unit instead to
> > use the base name as Free Pascal currently does in xlib.pp for example?
>
> I forked the xlib, xutils and x un
Am 18.08.2017 01:17 schrieb "Graeme Geldenhuys" <
mailingli...@geldenhuys.co.uk>:
>
> On 2017-08-17 21:47, Henry Vermaak wrote:
>>
>> You can use -l:libgreat.so.1 with gcc to link to a specific library
version
>> (iirc).
>
>
> I'll have to take your word for it Henry, as I don't know GCC much - onl
I see the common Linux port names got added to Synaser (trunk) but the BDS
variants (https://sourceforge.net/p/synalist/bugs/21/) wasn't added.
I've also just noted a typing error in GetSerialPortNames: '/dev/ttyAM*'
should rather be '/dev/ttyACM*''
On Thu, Aug 17, 2017 at 3:45 PM, Graeme Geldenh
20 matches
Mail list logo
