Hi, FPC developers!
I've commited patch to issue 9961 few days ago, and I'd like to ask if
someone could take a look at it? I'm currently analyzing several other
unit-loading issues (10551, 18294) with similar situations (relative
paths, different unit loading order when compiling and loading
On Mon, Mar 4, 2013 at 11:01 AM, Graeme Geldenhuys
gra...@geldenhuys.co.ukwrote:
On 2013-03-04 01:47, Boian Mitov wrote:
vast improvements of the code and the readability.
They are unreadable to me.
I recently started
rewriting our libraries with anonymous methods and that alone allowed
On Mon, Jan 7, 2013 at 6:05 PM, Mark Morgan Lloyd
markmll.fpc-de...@telemetry.co.uk wrote:
Tomas Hajny wrote:
On Mon, January 7, 2013 13:28, Ewald wrote:
Once upon a time, on 01/07/2013 12:39 PM to be precise, Michael Schnell
said:
On 01/05/2013 12:28 PM, Jonas Maebe wrote:
Using
On Tue, Aug 21, 2012 at 10:16 AM, Ivanko B ivankob4m...@gmail.com wrote:
Handling 1..4(6) bytes is less efficient than handling surrogate
*pairs*.
===
But surrogate pairs break array-like fast char access anyway, isn't it ?
It's also broken in UTF8 in the same way - so none of
On Tue, Aug 21, 2012 at 9:53 AM, Martin Schreiber mse00...@gmail.com wrote:
Am 21.08.2012 09:31, schrieb Graeme Geldenhuys:
Ehm, I did both. In the beginning MSEgui switched from Widestring to utf-8
encoded Ansistring because of the buggy FPC widestring implementation
(MSEgui started with
On Tue, Aug 21, 2012 at 11:41 AM, Mattias Gaertner
nc-gaert...@netcologne.de wrote:
Theoretically you could rewrite the FCL to support UTF8String,
UnicodeString and AnsiString. But not at the same time. In an
application there is always be only one of them. So you have to ship for
each flavor
On Wed, Jan 12, 2011 at 11:41, LacaK la...@zoznam.sk wrote:
3. C style comments: /* ... */ (I have never understood why in Pascal was
used (* ... *) )
Because they are much more clear and easy to understand (both for
compiler and for reader). C comments are very-very-very ugly. For
example,
Hi!
I've attached several patches regarding generics some time ago
(http://bugs.freepascal.org/view.php?id=15875,
http://bugs.freepascal.org/view.php?id=11777), but there was no
response regarding them. Is anyone from fpc developers working on
generics currently
On Mon, Jul 19, 2010 at 12:29, Hans-Peter Diettrich
drdiettri...@aol.com wrote:
The directive list contains records with the name and other attributes of
every directive, and with a reference to the directive handler procedure.
These handler procedures need further information, that currently
On Sun, Jul 11, 2010 at 06:47, Hans-Peter Diettrich
drdiettri...@aol.com wrote:
I know that the in filespec is part of the Delphi syntax, but what is it
really good for?
AFAIK it's not allowed to rename units this way, and since (currently)
only absolute filenames are implemented, I really
-devel
--
Aleksa Todorovic - Lead Programmer
Eipix Entertainment
www eipix com
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
,
- Graeme -
--
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://opensoft.homeip.net/fpgui/
___
fpc-devel maillist - fpc-de...@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
--
Aleksa Todorovic
On Wed, Jun 9, 2010 at 12:22, Graeme Geldenhuys graemeg.li...@gmail.com wrote:
Op 2010-06-09 12:08, Aleksa Todorovic het geskryf:
point of view regarding coordinates. You assume that integer
coordinates represent center of pixel, but they actually represent
top-left corner of pixel. In other
On Tue, May 18, 2010 at 11:52, Florian Klaempfl flor...@freepascal.org wrote:
Maybe (and really only maybe) the proper solution in this case are C++
styled template methods.
Different languages deal with this problem in different ways:
- C++ (Java) have powerful enough template (generics)
On Fri, Jan 29, 2010 at 08:56, Thaddy tha...@thaddy.com wrote:
Aleksa Todorovic wrote:
else is handled as part of if b then - the closest preceeding if:
This would break almost all my code.
Hm... it shouldn't. As far as I tested it, it correctly handles all
possible situations. If it doesn't
On Fri, Jan 29, 2010 at 08:09, Graeme Geldenhuys
graemeg.li...@gmail.com wrote:
Non-confusing end result looks like this:
if a then
begin
DoSomething;
end
else
begin
DoOtherThing;
end;
or
if a then
begin
DoSomething;
end
else begin
DoOtherThing;
end;
As
On Fri, Jan 29, 2010 at 10:22, Juha Manninen juha.manni...@phnet.fi wrote:
BTW, why doesn't the example code compile in current FPC?
I remember such code compiled in Delphi but I am not sure and I don't have
Delphi now to check.
Because FPC does not support semicolon before else :-)
On Fri, Jan 29, 2010 at 11:36, Juha Manninen juha.manni...@phnet.fi wrote:
It means there is no ambiguity and the patch can be applied without breaking
any code.
Or, is there some detail I have missed?
I have not found any problems, but since this is serious syntax
change, I cannot guarantee
On Fri, Jan 29, 2010 at 11:42, Michael Van Canneyt
mich...@freepascal.org wrote:
It breaks the behavious of case:
case b of
1 : something;
2 : If a then
DoSomethingElse;
else
DoElse
end;
As it is now, b=2 and a=False will result in no code executed.
After the patch, B=2 and
On Fri, Jan 29, 2010 at 12:11, Marc Weustink marc.weust...@cuperus.nl wrote:
Aleksa Todorovic wrote:
On Fri, Jan 29, 2010 at 11:42, Michael Van Canneyt
mich...@freepascal.org wrote:
It breaks the behavious of case:
case b of
1 : something;
2 : If a then
DoSomethingElse;
else
On Fri, Jan 29, 2010 at 13:23, Marco van de Voort mar...@stack.nl wrote:
Depends. I do see a minor point for e.g. ++ and --, since I have been bitten
by that when translating e.g. compression code (paszlib, lz77) when these
are used in complex nested loops.
Hopefully, it would be easy to
On Fri, Jan 29, 2010 at 16:22, Jonas Maebe jonas.ma...@elis.ugent.be wrote:
On 29 Jan 2010, at 16:12, Aleksa Todorovic wrote:
Depends. I do see a minor point for e.g. ++ and --, since I have been
bitten
by that when translating e.g. compression code (paszlib, lz77) when these
are used
On Tue, Jan 26, 2010 at 10:56, Juha Manninen juha.manni...@phnet.fi wrote:
Object Pascal is otherwise a nice language but there are few annoying syntax
details that other languages have solved better. Three such cases pop into my
mind:
1. This semicolon / no semicolon irritation.
I'm trying
On Fri, Jan 29, 2010 at 00:00, Juha Manninen juha.manni...@phnet.fi wrote:
How does your patch handle this? :
if a then
if b then
DoSomething;
else
DoOtherThing;
else is handled as part of if b then - the closest preceeding if:
program test3;
var
x: Integer;
begin
x :=
On Tue, Jan 26, 2010 at 07:42, Graeme Geldenhuys
graemeg.li...@gmail.com wrote:
As for the 'otherwise' syntax. You are correct, I have never heard or seen
it before. :-) But it is documented in the FPC Language Reference section
10.2.2.
On more probably less known reserved identifier is FAIL.
Thank you for your responses.
On Tue, Jan 26, 2010 at 08:23, Graeme Geldenhuys
graemeg.li...@gmail.com wrote:
Daniël Mantione wrote:
Indeed, it would be undesired to accept that semicolon. What makes me
uncomfortable is that he went to the trouble of modifying the compiler for
it. We should
On Tue, Jan 26, 2010 at 10:11, Marco van de Voort mar...@stack.nl wrote:
In our previous episode, Mark Morgan Lloyd said:
Agree. My primary intention was not to change official language, but
to try to make a change which will help me in my work. I just shared
it with others.
But in that
On Tue, Jan 26, 2010 at 10:44, Graeme Geldenhuys
graemeg.li...@gmail.com wrote:
Hi,
[snip
I gather FPC doesn't use something like this? If so, any specific
reason why not? It seems like a very easy way to extend the language
though. Simply describe the syntax and another program generates
On Tue, Jan 26, 2010 at 07:42, Graeme Geldenhuys
graemeg.li...@gmail.com wrote:
David W Noon wrote:
Example where 'do_3 is part of the case statement:
case p of
'1': do_1;
'2' if (q 0) then do_2;
else do_3;
end;
Example where 'do_3' is part of the '2' if/else statement:
On Tue, Jan 26, 2010 at 11:27, Michael Schnell mschn...@lumino.de wrote:
On 01/26/2010 07:51 AM, Daniël Mantione wrote:
We should encourage that.
Maybe from his work he could derive an acceptable patch that issues an
ambiguity warning just if a Semicolon decides between two
syntactically
Hi, all!
I used to work in Pascal (Delphi/fpc) for 10 years, and later had to
go to C++ (because of my day job). Now, I'm back to fpc, and one thing
I really miss is ability to have semicolon before else.
So, here's (attached) patch for fpc that makes it possible. The only
problematic place for
On Sun, Nov 15, 2009 at 23:26, Juha Manninen juha.manni...@phnet.fi wrote:
Hi,
[...]
Binary package fpc-2.4.0-0.rc1.i386.rpm installed fine after ignoring a
dependency for libtinfo.so.5. It seems to affect the text IDE only, not the
compiler and so is not a problem.
I've just tried to
On Thu, Nov 20, 2008 at 10:06, Graeme Geldenhuys
[EMAIL PROTECTED] wrote:
Unfortunately that doesn't work if the file contains unicode content,
so the following hack is required which is quite nasty:
ls := TStringList.Create;
ls.LoadFromFile('someunicodefile.txt');
for i := 0 to
Or... it could be implemented using generics, so one can choose:
TStringListUnicodeString
TStringListAnsiString
TStringListShortString
(sorry for C++ish syntax, but I hope you understand)
On Thu, Nov 20, 2008 at 15:07, Florian Klaempfl [EMAIL PROTECTED] wrote:
Graeme Geldenhuys schrieb:
Hi,
So, which action from right-click menu have you chosen? SVN Checkout?
--
Aleksa Todorovic
Lead Programmer
Eipix, Game Develoopment Company
www.eipix.com
On Fri, Nov 7, 2008 at 17:07, listmember [EMAIL PROTECTED] wrote:
I mean what command are you using. Something like:
svn co
On Fri, Sep 26, 2008 at 09:04, Graeme Geldenhuys
[EMAIL PROTECTED] wrote:
On Thu, Sep 25, 2008 at 10:33 PM, Florian Klaempfl
[EMAIL PROTECTED] wrote:
I suppose it would be viable doing timing results for saving text
files as well. After all, 99% of the time, text files are stored in
UTF-8.
Hi!
I've just hit this problem, and wanted to report it, so someone can
tell me if this is FPC or Lazarus bug.
==
Compiler version: 2.2.2
Lazarus version: svn trunk (revision 16671)
Description: If -Sh is used before -Mobjfpc on command-line, string is
interpreted as ShortString,
Thanks for the quick reply, I'll make bug-report immediately.
On Mon, Sep 22, 2008 at 14:00, Michael Van Canneyt
[EMAIL PROTECTED] wrote:
On Mon, 22 Sep 2008, Aleksa Todorovic wrote:
Hi!
As you can see, in the third case string is interpreted as
ShortString, not AnsiString
38 matches
Mail list logo
