Dr. Karl-Michael Schindler wrote:
Hi all,
In order to get fpc into fink, the darwin/macosx debian package manager
it would be necessary to make available a bootstrap tar ball (640 KB)
with the ppcppc binary and a default fpc.cfg file.
My suggestion would be the same dir as the fpc source tar
the fpc.cfg is just installed in ../etc as a default fpc.cfg file.
Am 20.03.2005 um 01:49 schrieb peter green:
note: a config file is NOT needed to compile freepascal itself the
makefiles
pass an option that tells the compiler to ignore it anyway.
-Original Message-
From: [EMAIL
I tried out valgrind on lazaraus and one of my own lcl programs, and was
able to get it working by after applying some small patches to valgrind
(which I have sent to the valgrind mailing lists). valgrind found some
uninitialised memory reads, which the attached patch fixes.
On a related
C Western wrote:
I tried out valgrind on lazaraus and one of my own lcl programs, and was
able to get it working by after applying some small patches to valgrind
(which I have sent to the valgrind mailing lists). valgrind found some
uninitialised memory reads, which the attached patch fixes.
Florian Klaempfl wrote:
C Western wrote:
I tried out valgrind on lazaraus and one of my own lcl programs, and
was able to get it working by after applying some small patches to
valgrind (which I have sent to the valgrind mailing lists). valgrind
found some uninitialised memory reads, which the
btw theese changes have already been committed (i sent them personally to
fpk). It seems like this mail was held for approval or something (i
previously thought it had been dropped)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of peter green
Sent: 11
El dc, 09-03-2005 a las 11:19, jordi escribiĆ³:
Hi, I send the catalan translation of errore.msg (v 1.119).
Sorry, I sent this message on march 9 ...and I receive the post
acknowledgement today ...
--
(Please, if you can answer use the list, otherwise I won't receive it.
Thanks)
Ales Katona wrote:
C++ requires friend only because it lacks the idea of modularity.
Since all classes are apart they need some way to tell each other I
can use you
In pascal you simply put them into 1 unit.
That's why the C++ model is better, there exists no requirement to
implement related
Michael Van Canneyt wrote:
sorry, but I fail to see the problem ? The above makes all protected
members of a class visible. This is normal, that is why they are
protected. If you want to avoid that, make the members private. Then
they are visible only in the same unit, even for other classes
Micha Nelissen wrote:
On Sat, 19 Mar 2005 10:04:55 +0100
DrDiettrich [EMAIL PROTECTED] wrote:
In porting C++ code to Pascal I often stumbled into circular unit
references. Then the only solution is a monster unit, that implements
all the related classes at once, where the C++ implementation can
Hi Ales,
on 2005-03-18T10:57:10+01:00 Ales wrote:
C++ requires friend only because it lacks the idea of modularity.
Since all classes are apart they need some way to tell each other I
can use you
In pascal you simply put them into 1 unit.
But IMCO this is not really a good OOP-like
Hi Uberto,
on 2005-03-11T18:35:45+01:00 Uberto wrote:
This is not a big issue, anyway could we avoid the endless list of such
similar hints compiling Lazarus and our program?
Don't make me wrong, I apreciate the hints of the compiler.
9 times out of 10 if I don't use a parameter in a
DrDiettrich wrote / napĆsal (a):
Ales Katona wrote:
C++ requires friend only because it lacks the idea of modularity.
Since all classes are apart they need some way to tell each other I
can use you
In pascal you simply put them into 1 unit.
That's why the C++ model is better, there exists
On Sun, 20 Mar 2005 19:02:06 +0100 (CET), Peter Vreman
[EMAIL PROTECTED] wrote:
Hi all,
As 1.9.6 has finally entered Debian, I'm now working on packages for
Why is the debian diff for 1.9.6 so big? It looks like it contains the
same files that are also available in install/doc and
14 matches
Mail list logo