On Saturday 31 of March 2012 15:35:32 Bernd Kreuss wrote:
Hello widgetset and Qt experts, I need some explanations to better
understand what is going on. I recently posted a thread
TCanvas.TextRect, subpixel antialiasing with Qt4 that also included a
small demo application and screenshots to
On Sat, 31 Mar 2012 13:55:59 +0200
Jürgen Hestermann juergen.hesterm...@gmx.de wrote:
Long ago I configured Lazarus to directly jump to an error (if it
occurs) on my home machine. On my machine at work I also want to
configure it that way but even after a desperate long search on all
And you're running on an AMD CPU?
In that case, I'm absolutely baffled
You shouldn't, I have reported it working on AMD in the mantis case
(http://bugs.freepascal.org/view.php?id=21515) and on the lazarus forum
(http://forum.lazarus.freepascal.org/index.php/topic,14881.msg89591.html#msg
Mattias Gaertner schrieb:
Each package has its own compiler options. For example the LCL units need
some flags like inlining and C style operators and some linker options.
Why isn't this simply added to the source files (compiler switches)? It
would be much easier, rock solid and would even
Mattias Gaertner schrieb:
AFAIR Turbo Pascal was pretty simple. I really liked it.
It supported only one target platform and the OOP came with Delphi.
OOP was already implemented in Borland Pascal.
Compare the compiler flags of TP and FPC. TP is a toy compared to FPC.
But what has all this
Decided to try FPDocmanager. The readme wasn't entirely clear to me.
What about a change like this? Additionally, might it not be better to
remove the entire paragraph I marked Obsolete?
Thanks,
Reinier
Index: examples/fpdocmanager/README.txt
Trying out FPDocManager.
Have somme comments/questions - sorry if these have been raised before:
1. What is the common documentation directory you are asked to select
when starting it for the first time? Does it contain your sources?
Compiled documentation? Would be nice if there were a bit more
On Sun, 01 Apr 2012 11:04:23 +0200
Jürgen Hestermann juergen.hesterm...@gmx.de wrote:
Mattias Gaertner schrieb:
Each package has its own compiler options. For example the LCL units need
some flags like inlining and C style operators and some linker options.
Why isn't this simply added
On Sun, 01 Apr 2012 11:20:49 +0200
Jürgen Hestermann juergen.hesterm...@gmx.de wrote:
Mattias Gaertner schrieb:
AFAIR Turbo Pascal was pretty simple. I really liked it.
It supported only one target platform and the OOP came with Delphi.
OOP was already implemented in Borland Pascal.
Mattias Gaertner schrieb:
That's exactly what I did. I used Larazus to create a console
application. I then added my general purpose unit to the uses clause.
Then compile failed with an error message that had nothing to do
with my
program or unit.
A console application is for simple
On Sun, Apr 01, 2012 at 12:52:02PM +0200, Mattias Gaertner wrote:
OOP was already implemented in Borland Pascal.
AFAIK this was only the object syntax, not the class syntax. IMO
the object syntax is too limited to be called true OOP.
TP Object syntax was perfectly valid oop. It provided
On 01/04/2012 14:15, Jürgen Hestermann wrote:
Mattias Gaertner schrieb:
That's exactly what I did. I used Larazus to create a console
application. I then added my general purpose unit to the uses clause.
Then compile failed with an error message that had nothing to do
with my
program or
Jürgen Hestermann schrieb:
Compare the compiler flags of TP and FPC. TP is a toy compared to FPC.
But what has all this to do with the concept of packages? The concepts
used in TP where enough to allow arbitrary complex applications. And my
main critic about all this is, that even when new
Mattias Gaertner schrieb:
On Sun, 01 Apr 2012 11:20:49 +0200
Jürgen Hestermann juergen.hesterm...@gmx.de wrote:
Mattias Gaertner schrieb:
AFAIR Turbo Pascal was pretty simple. I really liked it.
It supported only one target platform and the OOP came with Delphi.
OOP was already
Jürgen Hestermann schrieb:
Mattias Gaertner schrieb:
That's exactly what I did. I used Larazus to create a console
application. I then added my general purpose unit to the uses clause.
Then compile failed with an error message that had nothing to do
with my
program or unit.
A
Reinier Olislagers schrieb:
Decided to try FPDocmanager. The readme wasn't entirely clear to me.
What about a change like this? Additionally, might it not be better to
remove the entire paragraph I marked Obsolete?
The FPDocManager requires (parts of) FPC 2.7, so many users may wonder
why it
Reinier Olislagers schrieb:
Trying out FPDocManager.
Thanks for trying out, and for all your feedback :-)
Have somme comments/questions - sorry if these have been raised before:
1. What is the common documentation directory you are asked to select
when starting it for the first time? Does it
On 4/1/2012 05:04, Jürgen Hestermann wrote:
Mattias Gaertner schrieb:
Packages allow to share ppu files. You don't have to recompile
the LCL for every project. Each package has its own directory where its
ppu files are stored.
That's the concept of units. I just wonder why this is/was not
On Sunday 01 of April 2012 23:25:39 Bart wrote:
On 4/1/12, zel...@holobit.net zel...@holobit.net wrote:
Hi all,
As I've already mentioned few weeks ago on lazdevel, today we branched
1.0
:)
Nice indeed.
Whatever happened to 0.99, which as I understood would be the next
(and
19 matches
Mail list logo
