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
On 2017-08-18 08:15, Mark Morgan Lloyd wrote:
There's a
specific gotcha related to differences in the way Linux and Solaris
handle select(),
I saw some of those in th serial.pp in FPC trunk. Thanks for the
information.
I'm not aware of a reliable, cross-platform way of getting a complete
On 2017-08-18 01:10, kapibara via fpc-pascal wrote:
Your program was as
fast as No1 but anyway not visible among top ten.
Maybe the results backend uses higher precision result values, and the
web interface simply rounds it to two decimal places? ;-)
Regards,
Graeme
On 17/08/17 14:00, Graeme Geldenhuys wrote:
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
On 2017-08-18 08:16, Martin Schreiber wrote:
I checked with a simple library file, it seems that FPC strips the ".so*" part
from "external" names.
Exactly what I discovered too. :-/
So the only way to make version-safe binding units in
Free Pascal seems to be to use dlopen()/dlsym().
That
On Friday 18 August 2017 07:28:01 Martin Schreiber wrote:
> 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
On 2017-08-18 06:28, Martin Schreiber wrote:
Did you remove the various {$linklib} statements too?
Did you check all units which where included by "uses" statements?
Yes to both.
Regards,
Graeme
___
fpc-pascal maillist -
On 2017-08-18 07:51, Christo Crause wrote:
I've also just noted a typing error in GetSerialPortNames: '/dev/ttyAM*'
should rather be '/dev/ttyACM*''
My version also has the first instance (ttyAM*) with a comment "ARM
boards". Your implementation in the bug report looks a lot better than
what
On Friday 18 August 2017 10:56:47 Graeme Geldenhuys wrote:
> On 2017-08-18 08:16, Martin Schreiber wrote:
> > I checked with a simple library file, it seems that FPC strips the ".so*"
> > part from "external" names.
>
> Exactly what I discovered too. :-/
>
If one manually changes in link.res
"
On 18/08/17 07:45, Graeme Geldenhuys wrote:
On 2017-08-18 08:15, Mark Morgan Lloyd wrote:> There's a> specific
gotcha related to differences in the way Linux and Solaris> handle
select(),
I saw some of those in th serial.pp in FPC trunk. Thanks for the
information.
I've got this terrible
Tony,
Thank you for your proposals!
I will take them to heart and improve the docs accordingly. Some parts are
20 years old, so no surprise that they are not exactly correct any more...
Michael.
On Fri, 18 Aug 2017, Tony Whyman wrote:
There has been some heated discussion on the Lazarus
On 2017-08-18 10:34, Mark Morgan Lloyd wrote:
I saw some of those in th serial.pp in FPC trunk. Thanks for the
information.
I've got this terrible habit of inserting comments...:-)
You and I must be a rare breed of programmer then. :-)
Regards,
Graeme
On 2017-08-18 11:13, Mark Morgan Lloyd wrote:
please could we have the breaking version numbers
noted explicitly.
The 'fpdoc' tool already has support for that feature. The tag
in description files. I don't know if it has actually been used in FPC
class documentation though. I know I use it
There has been some heated discussion on the Lazarus lists on the
subject to character encodings etc. This has exposed several issues with
the FPC Manual that I wanted to record.
1. The char type
The manual says: "A Char is exactly 1 byte in size, and contains one
ASCII character. "
This
On 2017-08-18 10:27, Martin Schreiber wrote:
If one manually changes in link.res
hahaha... You read my mind, I was going to try that today in my lunch
time. :-)
So now all that FPC needs is a new compiler parameter to tell it how to
generate the linker parameters, and when the alternative
On 18/08/17 10:00, Tony Whyman wrote:
There has been some heated discussion on the Lazarus lists on the
subject to character encodings etc. This has exposed several issues with
the FPC Manual that I wanted to record.
Could I ask one thing on behalf of people who try to maintain code so
that
On 2017-08-18 10:27, Martin Schreiber wrote:
the application links without errors despite there is no libX11.so ->
libX11.so.6 link.
I quickly tested under FreeBSD 10.3. Even thought FreeBSD doesn't have
*-devel packages like Linux does. All ports packages (binary or build
from source)
>Maybe the results backend uses higher precision result values, and the web
>interface simply rounds it to two decimal places? ;-)
It seems most likely that the results are evaluated at more than 2 decimal
places. I don't know why they would only display 2 decimal places, 1/100th of
a second
On Fri, Aug 18, 2017 at 9:39 AM, Graeme Geldenhuys <
mailingli...@geldenhuys.co.uk> wrote:
> On 2017-08-18 07:51, Christo Crause wrote:
>
>> I've also just noted a typing error in GetSerialPortNames: '/dev/ttyAM*'
>> should rather be '/dev/ttyACM*''
>>
>
> My version also has the first instance
On Friday 18 August 2017 12:45:26 Graeme Geldenhuys wrote:
> On 2017-08-18 10:27, Martin Schreiber wrote:
> > If one manually changes in link.res
>
> hahaha... You read my mind, I was going to try that today in my lunch
> time. :-)
>
> So now all that FPC needs is a new compiler parameter to tell
20 matches
Mail list logo
