Hello,
I am trying to get back up to speed after a couple of years away from
FPC/Laz, and I hope I am not a P.I.T.A. ...
I searched the mail archive, but I found nothing.
I am using 'fpc 2.7.1', and debugserver does not compile/make for me.
Did I overlook a setting?
Thank you.
This is the
On 11/06/2012 07:44 PM, leledumbo wrote:
What is the best way to port 'private static final' member?
private class var (assuming you want to declare a variable).
private static final Set = STATIC_SET;
static {
STATIC_SET = new HashSet;
STATIC_SET.Add("A Value");
...
}
Static
On 11/07/2012 09:26 AM, bsquared wrote:
Hello,
I am trying to get back up to speed after a couple of years away from
FPC/Laz, and I hope I am not a P.I.T.A. ...
I searched the mail archive, but I found nothing.
I am using 'fpc 2.7.1', and debugserver does not compile/make for me.
Did I overl
On 2012-11-07 18:51, bsquared wrote:
> the debugserver server that is an example in fpGUI. I built that and it
> works. tiOPF was also suggested. I intend to look into it as well.
I use both of those. Just a small note that the tiOPF logging has a few
more convenience LogValue() etc methods,
Hmm, just a suggestion:
Change all calls to (I don't know if argument lists are the same, it's
been a long time)
Listen() to fpListen()
ShutDown() to fpShutDown()
Socket to fpSocket()
Bind() to fpBind()
Prefix symbols:
Family, port and addr symbols with `sin_`
Make sure that
On 11/07/2012 11:38 AM, Ewald wrote:
Hmm, just a suggestion:
Change all calls to (I don't know if argument lists are the same, it's
been a long time)
Listen() to fpListen()
ShutDown() to fpShutDown()
Socket to fpSocket()
Bind() to fpBind()
Prefix symbols:
Family, port
On 11/07/2012 11:29 AM, Graeme Geldenhuys wrote:
On 2012-11-07 18:51, bsquared wrote:
the debugserver server that is an example in fpGUI. I built that and it
works. tiOPF was also suggested. I intend to look into it as well.
I use both of those. Just a small note that the tiOPF logging has
In our previous episode, Ewald said:
> Change all calls to (I don't know if argument lists are the same, it's
> been a long time)
> Listen() to fpListen()
> ShutDown() to fpShutDown()
> Socket to fpSocket()
> Bind() to fpBind()
>
> Prefix symbols:
> Family, port and addr symbo
On 07/11/2012 20:41, bsquared wrote:
If I recall correctly you don't use Laz much; however, is it possible
that it could log to Laz messages window?
I don't think so. Don't think you can log to message window at all.
But debugger has an event window. You can set breakpoints, that do not
stop
Am 07.11.2012 18:33 schrieb "bsquared" :
> As an aside, I would like to note that after a couple of years away I
still see the same contributers in this list, and it is excellent to find
that support and commitment.
After all we have to keep the Pascal community living (or spoken in a
recent conte
On 11/07/2012 10:06 PM, Marco van de Voort wrote:
> In our previous episode, Ewald said:
>> Change all calls to (I don't know if argument lists are the same, it's
>> been a long time)
>> Listen() to fpListen()
>> ShutDown() to fpShutDown()
>> Socket to fpSocket()
>> Bind() to fpBin
On 11/07/2012 11:29 AM, Graeme Geldenhuys wrote:
On 2012-11-07 18:51, bsquared wrote:
the debugserver server that is an example in fpGUI. I built that and it
works. tiOPF was also suggested. I intend to look into it as well.
I use both of those. Just a small note that the tiOPF logging has
On 07/11/2012 19:41, bsquared wrote:
If I recall correctly you don't use Laz much; however, is it possible
that it could log to Laz messages window?
As Martin mentioned, I don't think you can log to the Laz messages
window - it just captures FPC output.
Regards,
- Graeme -
_
On 07/11/2012 22:13, bsquared wrote:
I like the tiOPF based Logging. Nice work.
It is the most reliable logging framework I know. For example, the
dbugintf unit in FPC has major issues when used under Windows. If you
generate many messages per second (which happens easily when you debug
V
14 matches
Mail list logo
