Since the earlier release on 23-Dec-2011 the file mentioned below has
been updated to FPC 2.6.0 and the serial debug terminal example also has
some improvements made.
Paul Breneman wrote on 23-Dec-2011:
I have posted a 3.9 MB zip file that has a minimal distribution of the
FPC 2.4.4 compiler
I filed the report here:
http://bugs.freepascal.org/view.php?id=21022 [4]
BTW, it think it has
to do with overloaded methods. Whenever fpdoc encounters such methods it
will enclose them in visibility directives.
Regards, Darius
On 4 jan
'12, Michael Van Canneyt wrote:
> On Wed, 4 Jan 20
On Wed, 4 Jan 2012, dhkblas...@zeelandnet.nl wrote:
Found some strange behaviour imho. For some reason there are extra visibility
sections inserted in my documentation, instead of following the source. I
expected fpdoc to respect the visibility directives instead of deciding
autonomously wh
Am 04.01.2012 15:56, schrieb leledumbo:
>> Are you connected via CABLE or WIRELESS
>
> Wireless, via USB modem. It works now using Jonas' suggestion.
>
Just a small hint: for read only use, svn2.freepascal.org is a much
better server: much faster than svn.freepascal.org and no MTU trouble.
Even
Hello FPC-Pascal,
Wednesday, January 4, 2012, 1:31:01 AM, you wrote:
MD> Very interesting and I agree when he say:
MD> "I think the reason programmers in C/C++/Java style languages have
MD> been attracted to exceptions is simply because the syntax does not
MD> have a concise way to call a functio
On 1/4/12, Pierre Free Pascal wrote:
> Did you try to "manually" (meaning with some other text editor, or sed
> script)
> remove the offending line -Cp386 from fp.cfg?
Yes, and that works.
> The problem might come from a fp.cfg that was created by an earlier
> version
> of Free Pascal for wh
On 4 January 2012 12:33, Malvin wrote:
> Is there any other components need installing so that it will connect
> properly other than libmysql.dll,
Under Windows, that should be all that you need. Under Linux you would
normally need to install the xxx-dev package where xxx is the database
library (
Found some strange behaviour imho. For some reason there are extra
visibility sections inserted in my documentation, instead of following
the source. I expected fpdoc to respect the visibility directives
instead of deciding autonomously when to place one.
See for example:
documentation:http
> Are you connected via CABLE or WIRELESS
Wireless, via USB modem. It works now using Jonas' suggestion.
--
View this message in context:
http://free-pascal-general.1045716.n5.nabble.com/FPC-JVM-checkout-problem-tp5116983p5119787.html
Sent from the Free Pascal - General mailing list archive at N
> The problem might still be related to the MTU. Maybe a patch since then has
exactly the "right" size to trigger the problem. Try lowering it a bit to
see what happens.
Hell yeah, I follow the suggestion in the thread to lower it down from 1500
to 1300 and it works! Thanks Jonas.
--
View this me
On 04/01/2012 12:49, Bernd wrote:
> 2012/1/3 Lars :
>
>> But that just a goto statement going to the except label.. Exceptions in a
>> way are actually forcing you to write your code in a GOTO way.
>
> I would see Exceptions as being more like the fabled COMEFROM, the
> legendary counterpart of
On 04 Jan 2012, at 14:14, ik wrote:
As I understand (I hope I'm wrong), memory allocations inside a signal
handler is unsafe. Is that true ?
Yes. The reason is that signals could be raised at any point during
the execution, including e.g. while a heap manager routine was already
being exe
Did you try to "manually" (meaning with some other text editor, or sed
script)
remove the offending line -Cp386 from fp.cfg?
The problem might come from a fp.cfg that was created by an earlier
version
of Free Pascal for which -Cp386 was allowed.
To complicate things further, once you tried t
Am 04.01.2012 14:20, schrieb Sven Barth:
Am 04.01.2012 14:14, schrieb ik:
Another question, is it possible to use exitproc if SIGKILL is sent, or
there is nothing I can do at all ?
SIGKILL is supposed to be the "last resort" of the system (or the user).
If it would be possible for the app to r
Am 04.01.2012 14:14, schrieb ik:
Another question, is it possible to use exitproc if SIGKILL is sent, or
there is nothing I can do at all ?
SIGKILL is supposed to be the "last resort" of the system (or the user).
If it would be possible for the app to react on SIGKILL it could do
things which
Hello,
I have read "man 7 signal" in Linux, and there are few sections regarding
safe and unsafe system calls to be used inside a signal handler.
As I understand (I hope I'm wrong), memory allocations inside a signal
handler is unsafe. Is that true ?
Further-more, I wish to reload configuration
On Wed, Jan 4, 2012 at 9:56 AM, Lukasz Sokol wrote:
> On 04/01/2012 12:47, Marcos Douglas wrote:
>
> [i see I hit on the obvious so: cut]
>
>>
>> I agree with you! But I was discussing the possibility do not using
>> Exceptions. ;-) Another point is when and where uses Exceptions...
>> that's what
On 04/01/2012 12:47, Marcos Douglas wrote:
[i see I hit on the obvious so: cut]
>
> I agree with you! But I was discussing the possibility do not using
> Exceptions. ;-) Another point is when and where uses Exceptions...
> that's what they were discussing.
>
> Marcos Douglas
Well I think the
2012/1/3 Lars :
> But that just a goto statement going to the except label.. Exceptions in a
> way are actually forcing you to write your code in a GOTO way.
I would see Exceptions as being more like the fabled COMEFROM, the
legendary counterpart of the GOTO.
On Wed, Jan 4, 2012 at 9:18 AM, Lukasz Sokol wrote:
> On 04/01/2012 11:50, Marcos Douglas wrote:
>
>> Ok, I expressed myself poorly.
>> When I said: "If we could return more than one value, ok we (maybe) do
>> not need Exceptions."
>> I mean: "If we could return more than one value, using a better
2012/1/2 Bernd :
> (I haven't yet understood the original asmcse implementation, not even
> partially, it looks incredibly complicated to me, it will immediately
> induce a coma-like trance whenever I try to read through it)
This wasn't meant as a criticism of the code, it was rather meant to
ill
On 04/01/2012 11:50, Marcos Douglas wrote:
> Ok, I expressed myself poorly.
> When I said: "If we could return more than one value, ok we (maybe) do
> not need Exceptions."
> I mean: "If we could return more than one value, using a better way
> than 'out arguments' or 'array of const', ok we (mayb
Am 03.01.2012 14:00, schrieb Frank Fischer:
Hi,
I'm a fpc newbie and currently playing around with generic classes.
Consider the following code:
[snip]
% fpc test.pas
Free Pascal Compiler version 2.6.0 [2011/12/23] for i386
Copyright (c) 1993-2011 by Florian Klaempfl and others
Target OS: Lin
I had the same issue when specifying a specific compiler in Lazarus. I
changed the directory back to
/usr/local/bin/ppc386
and it worked fine. I almost created another SymLink (as you did), and
since that obviously works as well, the issue seems to be that Lazarus looks
for fpcres in the same
Hi,
I'm a fpc newbie and currently playing around with generic classes.
Consider the following code:
= test.pas =
{$mode objfpc}
program Test;
type
generic TGen<_T> = class
public
type
TInner = class
procedure Func;
end;
end;
TInst = specialize TGen
On Wed, Jan 4, 2012 at 8:35 AM, Lukasz Sokol wrote:
>
> On 04/01/2012 00:31, Marcos Douglas wrote:
> [...]
> >> Another interesting article is:
> >> http://www.joelonsoftware.com/items/2003/10/13.html
> >
> > Very interesting and I agree when he say:
> > "I think the reason programmers in C/C++/Ja
On 04/01/2012 00:31, Marcos Douglas wrote:
[...]
>> Another interesting article is:
>> http://www.joelonsoftware.com/items/2003/10/13.html
>
> Very interesting and I agree when he say:
> "I think the reason programmers in C/C++/Java style languages have
> been attracted to exceptions is simply bec
Is there any other components need installing so that it will connect
properly other than libmysql.dll, and also i've heard of TMySQL, what is
that? and is there any other alternatives?
On Wed, Jan 4, 2012 at 9:48 AM, Malvin Viriya wrote:
> Thanks, I will try checking that site
>
>
> On Tue, Ja
28 matches
Mail list logo
