Luca Olivetti wrote:
En/na Jonas Maebe ha escrit:
On 14 jun 2007, at 19:04, Luca Olivetti wrote:
No suggestions? Is there some special option (apart from -g) that I
should specify to compile/link my program?
No. But the garbage backtrace means that either your gdb cannot parse
the signal h
Luca Olivetti wrote:
En/na Jonas Maebe ha escrit:
On 14 jun 2007, at 19:04, Luca Olivetti wrote:
No suggestions? Is there some special option (apart from -g) that I
should specify to compile/link my program?
No. But the garbage backtrace means that either your gdb cannot parse
the signal h
En/na Jonas Maebe ha escrit:
On 14 jun 2007, at 19:04, Luca Olivetti wrote:
No suggestions? Is there some special option (apart from -g) that I
should specify to compile/link my program?
No. But the garbage backtrace means that either your gdb cannot parse
the signal handler frame, or that
On Fri, 2007-06-22 at 10:43 +1000, John wrote:
> Joost van der Sluis wrote:
>
> > IN principle you can set ReadOnly to false and ParseSQL to true. That
> > way sqldb tries to parse your query. If it's a simple 'select * from
> > table' the TSQLQuery will be updateable. It automatically generates
>
> is it possible to tell fpc to only replace macros in the code and
> store/show the generated file?
> Like Running "cpp myfile.c > myfile.preprocessed.c"?
Not that I know. If it is really macro's you care about, you are out of
luck.
If you just want to get rid of conditionals, try the pascal p
Hi,
I'm pretty new to using interfaces... I want to use interfaces so that
I can spot problems at compile time and not runtime. For example: If
I used a base class with abstract methods and then created descendant
classes and forget to implement one of the abstract methods which gets
called some
On Friday 22 June 2007 06:27, Carsten Bager wrote:
> In the small threads program below I force a runtime error in a
> thread. How do I get access to the output from the thread when it
> stops? This program does not write anything to the terminal when the
> thread stops.
In case a runtime error oc
On Friday 22 June 2007 07:28, Michael Van Canneyt wrote:
> - Don't use synchronize to fire the timer, because that limits
> the use of timers to the main thread.
> This one is harder, and I must confess I don't have a clue
> on how to implement this in a platform independent manner...
Well,
