Op Tue, 5 Mar 2013, schreef Henry Vermaak:
Damn. My custom config kernel compiles stable kernels in 3-5 minutes on
a quad core Xeon, which isn't bad. Did you build with the standard
config?
What is the standard config? As the operating system is Scientific Linux
6, I'm using the config
Op Tue, 5 Mar 2013, schreef Mark Morgan Lloyd:
I've not had an opportunity to try this, but my understanding is that on a
Sun E10K with something like 256 400MHz processors the Linux kernel built in
around 20 seconds. I've had it build in about 3 minutes on a system with 16x
80MHz
Op Sun, 3 Mar 2013, schreef Marcos Douglas:
On Sun, Mar 3, 2013 at 5:16 PM, Graeme Geldenhuys
gra...@geldenhuys.co.uk wrote:
On 2013-03-03 19:47, Florian Klämpfl wrote:
First 10 m of a marathon done.
Is that 'miles' or 'meters'? ;-)
Sad. Instead of fight, why not walking together?
Op Mon, 4 Mar 2013, schreef Martin Schreiber:
In MSEgui development I am happy if users report what they need in their daily
work and what is inconvenient in current MSEgui implementation. I then try to
examine the problem, find out how it can be solved and implement an universal
solution
Op Mon, 4 Mar 2013, schreef Martin Schreiber:
On Monday 04 March 2013 12:05:37 Florian Klämpfl wrote:
Am 04.03.2013 01:00, schrieb Graeme Geldenhuys:
4.4 seconds (Kylix under Linux) vs 89 seconds (FPC under Linux)... That
is just too a huge performance difference to justify. Yes, we all
Op Mon, 4 Mar 2013, schreef Mattias Gaertner:
Is there no cache?
Something like: Give me all '+' operator overloads in all used units
of interface, implementation.
Actually a cache was part of my symtable redesign years ago. It never made
it into the compiler. But it was designed with a
Op Mon, 4 Mar 2013, schreef Mattias Gaertner:
Can this be cached?
Maybe the compiler can reuse some results?
No. The symtable lookups can be parsed, but the candidate selection, which
I believe is actually more compute intensive, is dependend on the actual
situation where the operator is
Op Mon, 4 Mar 2013, schreef Sven Barth:
Did you work out the concept somewhere?
It quite likely there is some archived copy of it in the old CVS
repository, but I am sure it's better to start from scratch. The compiler
was still using objects at that time, for example.
Op Mon, 4 Mar 2013, schreef Mattias Gaertner:
On Mon, 4 Mar 2013 14:37:40 +0100 (CET)
Daniël Mantione daniel.manti...@freepascal.org wrote:
Op Mon, 4 Mar 2013, schreef Mattias Gaertner:
Can this be cached?
Maybe the compiler can reuse some results?
No. The symtable lookups can
Op Mon, 4 Mar 2013, schreef Sven Barth:
It seems that I only achived around 0.1 to 0.2 seconds when compiling the
compiler (manually, with -B). But it's now checking only unit System and unit
constexp (part of the compiler) for operator overloads.
It's also interesting to see that not
Op Mon, 4 Mar 2013, schreef luiz americo pereira camara:
Is the bigger code just a side effect of a cross platform RTL or the
generated code is really bigger / slower?
There are again multiple reasons. One is indeed that the code is
multiple-platform and therefore some abstraction exist in
Op Sun, 3 Mar 2013, schreef Martin Schreiber:
BTW, a significant percentage of the time is waiting for FPC compiling because
FPC normally crashes without -B.
I think you should focus your efforts on getting those bugs fixed, such as
by submitting bug reports that allow reproduction of the
Op Fri, 25 Jan 2013, schreef Michael Schnell:
On 01/25/2013 11:12 AM, Michael Van Canneyt wrote:
Pchar ?
You seem to miss my point: the n'th printable character in an utf-8 coded
string (may same be stored as a pchar or a string) starts at the m'th byte
(m=n).
To find m for a given n
Op Sat, 26 Jan 2013, schreef Alexander Klenin:
With this in mind, consider a user who wants to iterate over the
following array:
var
a: array [1..5] of Integer = (1, 2, 9, 4, 5);
In my proposal, he should write:
var
v, i: Integer;
begin
for a in a index i do
Writeln(i, ' ', v);
end.
Op Sat, 26 Jan 2013, schreef Alexander Klenin:
var
a: array [1..5] of Integer = (1, 2, 9, 4, 5);
In my proposal, he should write:
var
v, i: Integer;
begin
for v in a index i do
Writeln(i, ' ', v);
end.
In this case I just write
for i:=low(a) to high(a) do
writeln(i,' ',a[i]);
Op Sat, 26 Jan 2013, schreef Alexander Klenin:
On Sat, Jan 26, 2013 at 5:12 AM, Daniël Mantione
daniel.manti...@freepascal.org wrote:
Consider these arguments:
1) Even for simple arrays, depending on array element type,
and optimizer implementation, for-in can be more efficient since it
can
Op Tue, 25 Sep 2012, schreef Cephas Atheos:
[My apologies for the previous message attempt - obviously the list server
doesn't handle html at all, and I could have checked for that first. Sorry
for the block of base64!]
G'day everyone,
As you may be aware, there are a number of significant
Op Sun, 16 Sep 2012, schreef Luca Olivetti:
but I don't know the outcome. Is it currently possible to develop software
for that mcu with freepascal?
As far as I know the Cortex M series cannot run generic ARM code; it only
understands the Thumb2 instruction set.
Op Tue, 11 Sep 2012, schreef Alexander Klenin:
On Tue, Sep 11, 2012 at 8:03 AM, Jonas Maebe jonas.ma...@elis.ugent.be wrote:
If you want to do that, you need to add a layer in between that converts the
sets into integer bitmasks in a reliable, portable and future-proof way.
How about
Op Mon, 10 Sep 2012, schreef Den Jean:
On Monday 10 September 2012 20:18:52 Vincent Snijders wrote:
If it is the combination of enum, then the type of the parameter is set of
enum.
Ahum, I am talking about passing combinations of enums values
(usually bitmasks, assigned enums, some assigned
Op Mon, 10 Sep 2012, schreef Jonas Maebe:
On 10 Sep 2012, at 22:06, Daniël Mantione wrote:
On Monday 10 September 2012 20:18:52 Vincent Snijders wrote:
If it is the combination of enum, then the type of the parameter is set of
enum.
Ahum, I am talking about passing combinations of enums
Op Mon, 10 Sep 2012, schreef Jonas Maebe:
If you want to do that, you need to add a layer in between that converts
the sets into integer bitmasks in a reliable, portable and future-proof
way.
Yes! Let's also convert integers to enums with a case statement rather
than typecast, just in
Op Mon, 10 Sep 2012, schreef Jonas Maebe:
On 10 Sep 2012, at 23:12, Daniël Mantione wrote:
Op Mon, 10 Sep 2012, schreef Jonas Maebe:
If you want to do that, you need to add a layer in between that converts the
sets into integer bitmasks in a reliable, portable and future-proof way
Op Thu, 23 Aug 2012, schreef Hans-Peter Diettrich:
Daniël Mantione schrieb:
Op Wed, 22 Aug 2012, schreef Felipe Monteiro de Carvalho:
On Wed, Aug 22, 2012 at 9:36 PM, Martin Schreiber mse00...@gmail.com
wrote:
I am not talking about Unicode. I am talking about day by day programming
Op Sun, 18 Mar 2012, schreef peter green:
My suspiscion was that the compiler was trying to spill but not actually
generating any code to implement the spill.
I added a debug writeln to setbitmap and it does seem to be being called with
both 50,70 and 70,50. Full output is at
Op Sat, 17 Mar 2012, schreef peter green:
I don't think my previous mail got through but if it does please disregard
it, my suspiscions as to the cause of the problem were incorrect.
While testing my armhf porting work I came across a case where parameters
were passed incorrectly to a
Op Sun, 18 Mar 2012, schreef peter green:
Daniël Mantione wrote:
Please use the command line option -sr to check the generated code before
register allocation.
Done and attatched.
You can likely find the cause in there.
The code with imaginary registers looks correct to me. It seems
Op Mon, 30 Jan 2012, schreef rvmart...@ntlworld.com:
michael.vancann...@wisa.be wrote the following on 30/01/12 14:49:53:
I think the reason for producing an ASCII version first is very simple:
All FPC sources - including the compiler - are in ASCII encoding.
I don't understand this
Op Mon, 30 Jan 2012, schreef steve smithers:
Hans-Peter Diettrich wrote on Mon, 30 Jan 2012 17:40:27 +0100
Existing source code frequently assumes ASCII encoding. The obvious are
upper/lowercase conversions, by and/or or add/sub constant values to the
characters. It will be hell to find and
Op Sun, 18 Sep 2011, schreef Torsten:
I do not know exactly which functions need to be changed. I'm hoping for tips.
You will have to be a bit exploring here; AVX is a major upgrade to the
x86 instruction set, and there will likely not be a few routines that need
to be changed.
First
Op Sun, 18 Sep 2011, schreef Florian Klämpfl:
I'am not sure if the ymm registers should be an own register class.
After all, they are a superset of xmm
Exactly. Since if xmm0 is allocated, ymm0 is allocated too; the register
allocator should treat them as a single register. xmm0 and ymm0
Op Thu, 7 Jul 2011, schreef Chad Berchek:
The problem comes down to the specs though, or rather the lack thereof. As I
have searched the web and read some docs at Embarcadero, things have only
become more ambiguous.
You are looking in the wrong places. Both Turbo Pascal and Delphi came
Op Sun, 15 May 2011, schreef Joerg Schuelke:
Am Sat, 14 May 2011 20:46:30 +0200 (CEST)
schrieb Daniël Mantione daniel.manti...@freepascal.org:
Inlining is better that doing the same with macro's, so is the use of
str/val better than macro tricks.
Wherever you can!
If I do some low level
Op Sat, 14 May 2011, schreef Joerg Schuelke:
2) This is the solution? Making the compiler to store somewhere a
string representation in my object file and then give it back to me if
I request it by str(enumerate)???
All types (not just enums) have runtime type information that is stored in
Op Sat, 14 May 2011, schreef Marco van de Voort:
2) This is the solution? Making the compiler to store somewhere a
string representation in my object file and then give it back to me if
I request it by str(enumerate)??? Thats so completely ... overhead,
Not really, if the RTTI is too slow
Op Sat, 14 May 2011, schreef Joerg Schuelke:
Am Sat, 14 May 2011 12:14:52 +0200
schrieb Florian Klämpfl flor...@freepascal.org:
Because a lot of code in the compiler is very old (remember, it was
started in 1993 using TP) and writestr for enums is new compare with
this time span. Nobody
Op Sat, 14 May 2011, schreef Joerg Schuelke:
I think of this a little different. Maybe more from an other
perspective. For me RTTI is a level of language extension. Like OOP, or
generics, or inheritance. Macros are very low level (if you have them).
RTTI *allows* for language extensions,
Op Fri, 29 Apr 2011, schreef Skybuck Flying:
I just had an idea how to better layout floats and such. The old way of
laying them out in writeln can be used which I love and is great:
Example:
begin
s := vSomeFloat:16:16 + ' ' + vSomeFloat:16:16;
end;
Good, then you really need to look
Op Fri, 29 Apr 2011, schreef michael.vancann...@wisa.be:
I wonder why FPC broke Delphi compatibility by adding {$MODE}, instead of
choosing its own prefix for added compiler directives and macros.
Because it would mean yet another kind of directive, this is confusing.
My take on it is
Op Wed, 20 Apr 2011, schreef Hans-Peter Diettrich:
Of course there exists no general rule, it depends on the concrete purpose of
a calculation, which algorithm, precision and type (BCD, fixed point...)
yields the best results. But there also exists no reason why a coder should
be prevented
Op Tue, 19 Apr 2011, schreef Nikolai Zhubr:
19.04.2011 14:12, Daniël Mantione:
MS does preserve FPU states between processes. You can use the x87 on
Windows, nothing prevents you from doing so. Maybe the calling
Yes it does for 32-bit processes on win64, guaranteed.
But do you have any
Op Tue, 19 Apr 2011, schreef Florian Klämpfl:
It's just that the documentation tells you not to use the x87.
Yes, because it's strange programming model should be really dropped.
Agree, but the 80 bit support makes some people want to use it. And that
will stay this way until CPU
Op Mon, 18 Apr 2011, schreef Hans-Peter Diettrich:
Sven Barth schrieb:
On Windows 64-bit you must not use the x87 FPU, because Microsoft wants it
so.
Can you be a bit more concrete?
Originally MS spread info it wouldn't work at all under Windows, but that
proved to be false, the FPU
Op Sun, 17 Apr 2011, schreef Sven Barth:
On Windows 64-bit you must not use the x87 FPU, because Microsoft wants it
so. Thus on Win64 Extended=Double.
On other x86_64 based operating systems the state might be different.
You can use the x87 on Linux. Don't know for FreeBSD, but I expect
Op Sat, 9 Apr 2011, schreef Florian Klämpfl:
Am 09.04.2011 21:04, schrieb Sergei Gorelkin:
09.04.2011 22:26, Sergei Gorelkin ?:
09.04.2011 22:13, Jonas Maebe ?:
Simply changing the register order in the array to trgcpu.create in
Tcgx86_64.init_register_allocators should do it.
Op Fri, 3 Dec 2010, schreef Thaddy:
If you all say no, I will live with it.
Could you maybe specify what you want to achieve and in what way FPC
requires you to use workaround hacks?
Daniël___
fpc-devel maillist -
Op Fri, 3 Dec 2010, schreef Thaddy:
On 3-12-2010 15:50, Daniël Mantione wrote:
Could you maybe specify what you want to achieve and in what way FPC
requires you to use workaround hacks?
Daniël
Yes,
In FPC the console IO is *always* redirected, be it through a handle or a
named file
Op Thu, 30 Sep 2010, schreef Mattias Gärtner:
When it is used for quick syntax check the compiler is invoked several times
a minute - several thousand times a day. Is that a problem?
Expect a few kilobytes that are left over at maximum, the compiler is
been debugged for memory leaks,
Op Wed, 29 Sep 2010, schreef Hans-Peter Diettrich:
A last note on the NoGlobals branch, and parallel processing in the compiler:
A few comments:
You seem to be reasoning from theory, and mainly OOP theory. In principle
this is good, I have been reasoning from theory in the past as well,
Op Mon, 13 Sep 2010, schreef Graeme Geldenhuys:
Op 2010-09-13 13:47, Martin Schreiber het geskryf:
I can not use resource strings because FPC resource strings are not unicode
capable AFAIK.
Probably related to your choice of UCS-2 - I don't really know the specific
issues you have, so it
Op Fri, 10 Sep 2010, schreef Hans-Peter Diettrich:
Sergei Gorelkin schrieb:
When dynamic strings are used all around, is the use of pointers to
ShortString still recommended? (fmodule contains a lot of them)
Whenever you care about performance, you'll quickly realize that dynamic
strings
Op Sun, 29 Aug 2010, schreef Hans-Peter Diettrich:
Copyright is about creative decisions. For example the order in
which procedures, variables are declared are creative decisions
and thus part of the expression of an interface. If you make
the same creative decisions as the original
Op Sun, 29 Aug 2010, schreef Paul Ishenin:
29.08.2010 21:39, Dimitri Smits wrote:
At the present state of fpc compiler it is technically imposible to
port
delphi rtti unit. To do this you need first to implement the next
compiler features:
1. Extended records (methods, class operators)
2.
Op Sat, 28 Aug 2010, schreef Dimitri Smits:
Hi,
(just hate it when you send something after re-reading it a few times, and a
minute later you know that there is something important you forgot to ask)
Since objectnames and interfaces are cloned from Delphi everywhere in the
fpc-rtl, I was
Op Tue, 10 Aug 2010, schreef Michael Schnell:
Finally I think that there is a decent chance to modify the compiler and the
RTL in a way that threadvars can be used fast and without needing a libc
binding
Yes there is. I worked on this a long time ago, but I didn't finish it.
The code
Op Wed, 28 Jul 2010, schreef Florian Klaempfl:
Am 28.07.2010 15:10, schrieb Hans-Peter Diettrich:
Florian Klaempfl schrieb:
IMO we should have at least an option, that a function name can *not* be
used for the function result any more, for the result we have the Result
variable. Then we
Op Wed, 28 Jul 2010, schreef Hans-Peter Diettrich:
Daniël Mantione schrieb:
If I understand it well this patch will disable not only the fpc
externsion:
writeln(name_of_function);
... but also the standard Pascal:
name_of_function:=value;
Why would we want to disable the standard Pascal
Op Mon, 19 Jul 2010, schreef Michael Schnell:
On 07/19/2010 03:11 PM, Jonas Maebe wrote:
That's correct. FPC has largely platform-independent support for
threadvars, which is much more heavy-weight than simply using a segment
register (indirect procedure call depending on the thread
Op Mon, 19 Jul 2010, schreef Sven Barth:
Hi!
Yes, though I am still puzzled how it works on x86_64; it seems regvars
there are also accessed using fs, but x86_64 prevents you from writing
to segment registers.
As mentioned here http://en.wikipedia.org/wiki/X86_64#Windows in the 10th
Op Mon, 19 Jul 2010, schreef Hans-Peter Diettrich:
Michael Schnell schrieb:
I do know that gcc in Linux on X86 uses a segment register. I don't know
how gcc works in Windows, but I suppose even Windows is assumed to restore
all register values of a thread after a preemption.
Windows
Op Fri, 16 Jul 2010, schreef Micha Nelissen:
Daniël Mantione wrote:
Compiler speed can loose from maintainability, but it can also loose from
code quality; the performance of your application is probably also worth a
lot to you.
Does FPC compile significantly faster when using -O
Op Fri, 16 Jul 2010, schreef Micha Nelissen:
Daniël Mantione wrote:
Op Fri, 16 Jul 2010, schreef Micha Nelissen:
Does FPC compile significantly faster when using -O- then?
That is irrelevant; for example the register allocator made the compiler
slower (initially even 3 times, but we
Op Thu, 15 Jul 2010, schreef Hans-Peter Diettrich:
This is what I'm going to do now.
Does there exist some profiling code already, or do I have to reinvent the
wheel?
No, simply use the -pg compiler option, the use gprof.
Daniël___
fpc-devel
Op Thu, 15 Jul 2010, schreef Graeme Geldenhuys:
maintainability is more important to the core team that speed.
No. That is doesn't do justice to all the effort that is put into
performance optimization. It's not about maintainability being more
important.
It is about making the right
Op Wed, 14 Jul 2010, schreef Hans-Peter Diettrich:
IMO compiler messages slow down compilation a lot.
How do you know this, did you benchmark or is it just your opinion?
When messages are not really output (prevented by message level...),
then a lot of procedure calls and string
Op Mon, 12 Jul 2010, schreef Michael Schnell:
On 07/12/2010 08:12 AM, Michael Van Canneyt wrote:
So for historical reasons, FPC is stuck with the 'in' clause, when in fact
it should
not exist in the first place.
It could be made useful when
You may be able to make it more usefull, but
Op Sun, 11 Jul 2010, schreef Hans-Peter Diettrich:
I know that the in filespec is part of the Delphi syntax, but what is it
really good for?
In my opinion, it is not usefull. I have never seen a clear description of
what the semantics should be, for example what happens if the code being
Op Thu, 24 Jun 2010, schreef Michael Schnell:
On 06/23/2010 05:35 PM, Daniël Mantione wrote:
It's a non-issue. If you set a thread realtime you know what you are
doing and can take care you give up the CPU when feasible, or you
simply don't enter mutuxes shared with non-realtime threads
Op Wed, 23 Jun 2010, schreef Graeme Geldenhuys:
Op 2010-06-22 15:31, Marco van de Voort het geskryf:
Same problem. You still have to interface with the kernel, and it would be
incompatible with C libraries that use threads.
Well, if I don't use C libraries (only Object Pascal code), then
Op Wed, 23 Jun 2010, schreef Henry Vermaak:
On 23 June 2010 13:58, Michael Schnell mschn...@lumino.de wrote:
On 06/23/2010 02:45 PM, Henry Vermaak wrote:
I think you'll first have to worry porting fpc to those architectures.
Right you are :)
But anyway, if not using libc, you need to do
Op Wed, 23 Jun 2010, schreef Henry Vermaak:
A futex syscall doesn't know anything about threads, it's for locking.
Perhaps I'm misunderstanding you?
I have should have written futex instead of threads. With a Futex, you
only call the Futex syscall, if the Futex is locked. You still have to
Op Wed, 23 Jun 2010, schreef Michael Schnell:
On 06/23/2010 05:18 PM, Mattias Gaertner wrote:
What system has such an unfair scheduler?
A fair Scheduler only can be fair if time slices are to be managed. If
you set a thread to a realtime priority (OK, you need to be root to be
allowed to
Op Mon, 1 Feb 2010, schreef Marco van de Voort:
In our previous episode, Michael Schnell said:
D2009/d2010 are still windows only.
Do you think there is any general problem in using D2009 strings with
dynamic encoding with Unix ? On the first view I don't see one.
In general I prefer to
Op Mon, 1 Feb 2010, schreef Marco van de Voort:
In our previous episode, Dani?l Mantione said:
Some commercial unices are also using utf-16 afaik, since they haven't
switched their TTY to UTF-8 yet. To be investigated.
I lean towards RTLString=utf8string; and RTLString=unicodestring on the
Op Sun, 31 Jan 2010, schreef Paul van Helden:
Of course Thanks Cobines!
I have never used the function name instead of Result, but of course you
can. Using () after a function to me seems so C-like and un-Pascallish but it
works.
But it is things like this that trip up people coming
Op Tue, 26 Jan 2010, schreef Graeme Geldenhuys:
David W Noon wrote:
Syntax and understanding is as clear as rain. Adding extra semi-colon, as
you suggested, is not.
Indeed, it would be undesired to accept that semicolon. What makes me
uncomfortable is that he went to the trouble of
Op Tue, 19 Jan 2010, schreef Graeme Geldenhuys:
Michael Van Canneyt wrote:
Why should it be better ? It doesn't really matter anyway.
PtrUInt has a larger range than PtrInt (allowing full access to memory
address range). Plus, I don't think pointers can be negative values.
The problem
Op Tue, 19 Jan 2010, schreef Dariusz Mazur:
Is this possible to forbid this at compile time?
An easy solution is to wrap it inside a record. This is good practise as
it prevents accidental bugs like accidentally writing parameters in the
wrong order when calling a procedure. It's
Op Thu, 10 Dec 2009, schreef Graeme Geldenhuys:
Paul Ishenin wrote:
This is delphi 2010 compatible behavior. Only info about published
methods is not written for classes with {$M-}.
So what is the correct way of asking if a class as RTTI (published
properties) available? Because
Op Sun, 16 Aug 2009, schreef Jonas Maebe:
On 16 Aug 2009, at 12:15, Nikolay Nikolov wrote:
Does anyone have an idea why the call to DoneKeyboard was previously
commented? It leaves the keyboard in a bad state if the IDE crashes.
It was changed in revision 3443, whose log message says:
Op Sun, 16 Aug 2009, schreef Nikolay Nikolov:
On 08/16/2009 03:22 PM, Daniël Mantione wrote:
Op Sun, 16 Aug 2009, schreef Jonas Maebe:
On 16 Aug 2009, at 12:15, Nikolay Nikolov wrote:
Does anyone have an idea why the call to DoneKeyboard was previously
commented? It leaves
Op Wed, 29 Jul 2009, schreef Desmond Coertzen:
This is my first question / suggestion: With byte sized variables being the
smallest accessible variable in the PC architecture, will we see a language
extension to provide bit accessible variables for the micro controllers?
Do you mean
Op Wed, 29 Jul 2009, schreef Desmond Coertzen:
That is fantastic!
Is this correct for application?
var
SomeIOPort: nibbles;
begin
SomeIOPort.low[7] := 1;
end;
nibbles is not an array?
Anyway, you can created bitpacked arrays, so the idea will work.
Op Thu, 23 Jul 2009, schreef Michael Schnell:
I'd really appreciate the 32 Bit PIC stuff, as this is MIPS and I might
want to do a NIOS port some day and the NIOS ISA is said to be quite
similar to MIPS (even the names are only a few bits apart :) )
The main challenge for a MIPS port is the
Op Thu, 11 Jun 2009, schreef Michael Van Canneyt:
On Thu, 11 Jun 2009, Jonas Maebe wrote:
I would think it is a natural extension of procedural overloading ?
It's not that simple. Properties can be both hidden variable access as
well as procedure access. Variable overloading is not
Op Fri, 5 Jun 2009, schreef Paul Ishenin:
How difficult is to teach compiler to remove them during compilation?
I sense a hope that somehow the compiler developments will ultimately be
able to turn large Lazarus executables into small ones. It is not
realistic.
The WPO features Jonas is
Op Mon, 1 Jun 2009, schreef Graeme Geldenhuys:
How do you mark a unit as deprecated?
In the user.pdf I have seen many references to units being deprecated
(eg: graph, oldlinux, etc), but I have only seen that being mentioned
in the documentation. There doesn't seem to be any compiler
Op Sun, 31 May 2009, schreef Jonas Maebe:
Yes, the but the results are not very impressive. The reason is due to the
way the LCL is constructed, almost every declared class can theoretically be
instantiated. On the other hand, I read that recently the LCL was
restructured a bit to improve
Op Tue, 5 May 2009, schreef Michael V. Denisenko:
A question appeared when I tried to find a method of generating
case-expression just once, not for every comparison. Is it optimal to
try to add for every case-structure (and do...while, by the way) a
temporary variable where we may hold the
Op Tue, 28 Apr 2009, schreef Vincent Snijders:
Tomas Hajny schreef:
On Tue, April 28, 2009 12:13, sakesun roykiatisak wrote:
Is it possible to remove dependency on cygwin from freepascal ?
To make it clear, I actually mean remove dependency on some cygwin
utilities
Fpc compiler is not
Op Sat, 18 Apr 2009, schreef Paul Ishenin:
Hello, FPC developers' list
I've found one interesting tool for delphi which I really want to have for
lazarus and fpc: http://delphitools.info/samplingprofiler/
To work that tool uses map files which generates delphi. I contacted to
author and
Op Sat, 18 Apr 2009, schreef Bogus?aw Brandys:
Daniël Mantione pisze:
Op Sat, 18 Apr 2009, schreef Paul Ishenin:
Daniël Mantione wrote:
Can fpc team extend output made by -Xm with line info?
Not if the GNU linker is used, which is the case for the majority of
platforms.
So -Xm
Op Sat, 18 Apr 2009, schreef Mike Denisenko:
Hello everyone, I'm a student of FESU, Russia. I've started to develop a feature - string
cases (Topic: Easiest way to case strings,
http://www.lazarus.freepascal.org/pipermail/lazarus/2009-March/023369.html), and now some
questions appear:
Op Fri, 13 Mar 2009, schreef Constantine Cusulos:
I would like to compile fpc on my OpenBSD4.4/i386 system. The buildfaq
(http://www.stack.nl/~marcov/buildfaq.pdf) requires to have a usable fpc
binary in order to compile fpc source.
OpenBSD has emulation for binaries from linux and FreeBSD
Op Thu, 12 Mar 2009, schreef Vincent Snijders:
Graeme Geldenhuys schreef:
On Wed, Mar 11, 2009 at 6:11 PM, Martin Schreiber fp...@bluewin.ch wrote:
Delphi/Kylix probably can't map a variable to the address of another
variable,
because of that Delphi needs separate implementations of format
Op Mon, 2 Mar 2009, schreef Alexander Klenin:
Since issue http://bugs.freepascal.org/view.php?id=13256 was marked resolved,
I think this is quite reasonable to expect this to work.
The writeability of constants is IMNSHO just an ugly leftover from
Delphi history,
and should be disabled in
Op Mon, 2 Mar 2009, schreef Alexander Klenin:
On Mon, Mar 2, 2009 at 03:16, Daniël Mantione
daniel.manti...@freepascal.org wrote:
Making typed constants writeable has been a disputed feature of the Borland
dialect, I agree with that, but fact of the matter is they are writeable and
thus
Op Sun, 11 Jan 2009, schreef Joost van der Sluis:
{$calling cdecl}
...
procedure fftw_execute(plan:fftw_plan_single);
external 'fftw3f' name 'fftwf_execute'; // -- register
{$calling register}
How can that happen?
It may have to do something with the proceduren not being processed
Op Tue, 2 Dec 2008, schreef Michael Schnell:
Nobody talks in this case about UTF-8. Even *ANSIstrings* in there
native meaning can contain multi byte chars, there are *multi byte* ansi
char sets.
If there is a widely used multi-byte ANSI encoding, why so we need Unicode ?
IMHO the
Op Tue, 2 Dec 2008, schreef Michael Schnell:
Thanks for pointing this out.
GB2312 suits them well. Likewise, JIS 0213 suits the Japanese well.
Are these called ANSI ?
Yes, code page 936 and code page 932 are valid ANSI code pages.
These standards by themselves of course not, because
1 - 100 of 556 matches
Mail list logo
