On 2011/07/18 12:00 PM, Marco van de Voort wrote:
No, it is more wiki like tags in an XML format. But that is out of source
docs, what is currently most prefered by the documentation author. (and I
like it more to)
Are you aware of NaturalDocs (www.naturaldocs.org)?
I use it because it doesn
> Based on this promise, the compiler may decide to do some optimization.
> It will also warn you if it detects inside the code that you break
> your promise.
Based on my new knowledge of const strings I revisited the bug I
mentioned previously. I still have no idea where exactly I made the
error.
>
> We also have to remember that *probably almost nobody* remembers
> fixing a bug related to this. That's because most people who come up
> against this bug probably have no clue what is happening and only by
> making some other changes do they coincidentally "fix" it. I propose
> that for a pr
Marco van de Voort wrote:
Yes, but from what I remember it was canceled because the amount of
periphery on the chip is poor. I also looked at ARM, but while there is more
choice there, it is fragmented over multiple vendors, with multiple
toolchains (if a free one exists at all)
What was can
Did you have a look at AVR?
They use GCC, although commercial compilers are also available should
you need it. I have used GCC-AVR for years without problems.
Marco van de Voort wrote:
In our previous episode, Michael Schnell said:
Which is that then? Afaik the microchip own, and the Hit
OK it is logged.
Jonas Maebe wrote:
On 05 Aug 2009, at 13:55, Wimpie Nortje wrote:
program memleak;
{$mode objfpc}{$H+}
uses
cthreads;
begin
end.
If I run the program using valgrind I get the following output:
==1944==Invalid free() / delete /
delete
Hi everybody,
The program:
program memleak;
{$mode objfpc}{$H+}
uses
cthreads;
begin
end.
If I run the program using valgrind I get the following output:
==1944==Invalid free() / delete /
delete[]
==1944==at 0x4025DFA: f
