Using OS X 10.6.1, FPC 2.2.4, Xcode 3.2 on intel iMac.
The program and units all have {$I Directives.inc} at top of each
file. Compile lists many errors like:
6: Mode switch "OBJFPC" not allowed here
Any hints?
___
fpc-pascal maillist - fp
On 09 Oct 2009, at 19:57, Paul Davidson wrote:
Using OS X 10.6.1, FPC 2.2.4, Xcode 3.2 on intel iMac.
The program and units all have {$I Directives.inc} at top of each
file. Compile lists many errors like:
6: Mode switch "OBJFPC" not allowed here
Any hints?
This is unrelated to Mac OS
In our previous episode, Jonas Maebe said:
> > Using OS X 10.6.1, FPC 2.2.4, Xcode 3.2 on intel iMac.
> >
> > The program and units all have {$I Directives.inc} at top of each
> > file. Compile lists many errors like:
> >
> > 6: Mode switch "OBJFPC" not allowed here
> >
> > Any hints?
>
> This
You said C did it "wrong", because you think that arrays and pointers
should be different things. That is indeed you opinion, not a fact.
I don't even know why I'm replying any more, it's clearly futile.
Huh? Are you seriously trying to tell us that pointers and arrays are
the same? Ok, then y
As said it depends from your viewpoint. C's original viewpoint was to keep
the state of a compilation unit as small as possible, to maximize the size
of a program with limited memory.
You mean they gave saving one character in the source code a higher
priority than having a strict logic in the
Jürgen Hestermann schrieb:
>> As said it depends from your viewpoint. C's original viewpoint was to
>> keep
>> the state of a compilation unit as small as possible, to maximize the
>> size
>> of a program with limited memory.
>
> You mean they gave saving one character in the source code a higher
And the criticism about introducing Cisms in FPC/Delphi is also old. In the
past I would have joined you, but after a few non-trivial header conversions
and library conversions that pretty much died out.
But why are you then using Pascal at all? I love this language because
of its strict logic
No, it happens with static arrays, if you set pia := @ia, ia[x] and
pia[x] will give you the same result (in delphi mode, at least).
It's simply more readable and a shortcut.
It's definitely the opposite: It is *less* readable because it leaves it
unclear what data you are operating with. Enu
Jürgen Hestermann schrieb:
>>> No, it happens with static arrays, if you set pia := @ia, ia[x] and
>>> pia[x] will give you the same result (in delphi mode, at least).
>> It's simply more readable and a shortcut.
>
> It's definitely the opposite: It is *less* readable
This is your opinion :) To
In our previous episode, J?rgen Hestermann said:
> > And the criticism about introducing Cisms in FPC/Delphi is also old. In the
> > past I would have joined you, but after a few non-trivial header conversions
> > and library conversions that pretty much died out.
>
> But why are you then using Pa
Remember, Pascal is merely a TEACHING language, unsuitable for commercial
software development, which is why we have C. :)
And why should that be the case? What are the outstanding feature of C
that make it so supperiour? It's illogical and hard to maintain syntax?
Or is it just that it was a
Am Montag, 12. Oktober 2009 11:02 schrieb Jürgen Hestermann:
> > Remember, Pascal is merely a TEACHING language, unsuitable for commercial
> > software development, which is why we have C. :)
>
> And why should that be the case? What are the outstanding feature of C
> that make it so supperiour? I
> Remember, Pascal is merely a TEACHING language, unsuitable for commercial
> software development, which is why we have C. :)
That's what I'm going to change. I've told my friends and collegemates about
Pascal superiority (suitable for any programming needs, GUI, WebApps,
Server, etc.) and the
Am Montag, 12. Oktober 2009 12:05 schrieb leledumbo:
> you don't need lazarus just to use fpc, and I don't need that debian
> testing system on my kubuntu.
Which editor do you use?
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.
Zitat von Rainer Stratmann :
Am Montag, 12. Oktober 2009 11:02 schrieb Jürgen Hestermann:
> Remember, Pascal is merely a TEACHING language, unsuitable for commercial
> software development, which is why we have C. :)
And why should that be the case? What are the outstanding feature of C
that
2009/10/12 Rainer Stratmann :
>
> Which editor do you use?
I'm not the one you replied to, but I can answer based on my
experience. I never use APT for FPC or Lazarus because they update
packages to slowly. I work directly from the Git mirror repositories.
* If I'm at work or home, I use Lazarus
Yes, it is available everywhere.
And it is easier to copy unix code then.
Remember that it is still not easy to come to freepascal.
You have to configure a debian testing system and apt-get lazarus and so on...
Nearly nowhere the lazarus package is preinstalled.
Yes, these are the reasons for ha
In our previous episode, Rainer Stratmann said:
> > > Remember, Pascal is merely a TEACHING language, unsuitable for commercial
> > > software development, which is why we have C. :)
> >
> > And why should that be the case? What are the outstanding feature of C
> > that make it so supperiour? It's
2009/10/12 Marco van de Voort :
>>
>> Yes, it is available everywhere.
>
> Try compiling some Unix C code on Windows.
>
> Give me Free Pascal any time :-)
+1
...and Try compiling some Unix C code on Unix/Linux/etc. I always
battle. Give me Free Pascal too! :-)
PS:
Wow, did this message thread
Am Montag, 12. Oktober 2009 12:31 schrieb Jürgen Hestermann:
> > Yes, it is available everywhere.
> > And it is easier to copy unix code then.
> > Remember that it is still not easy to come to freepascal.
> > You have to configure a debian testing system and apt-get lazarus and so
> > on... Nearly
No, it happens with static arrays, if you set pia := @ia, ia[x] and
pia[x] will give you the same result (in delphi mode, at least).
It's simply more readable and a shortcut.
It's definitely the opposite: It is *less* readable
This is your opinion :) To my experience faking arrays with dyn. si
On 11 Oct 2009, at 18:37, Matthias Klumpp wrote:
On Sun, 11 Oct 2009 11:09:58 +0200 (CEST), mar...@stack.nl (Marco
van de
Voort) wrote:
In our previous episode, Matthias Klumpp said:
also be in 2.4.0
I do not have problems with FPC 2.3.x, but it is not allowed for
me to
use
experimenta
p
The value of a pchar.
What do you mean by "value"? The pointer or the character it is pointing
to? It seems that p sometimes means the first and sometimes the latter.
p^
the char pointed to.
Is this the same as p?
I don't think you can say anything from pure syntax without bringing
On Mon, Oct 12, 2009 at 12:47, Jürgen Hestermann
wrote:
> No, it happens with static arrays, if you set pia := @ia, ia[x] and
> pia[x] will give you the same result (in delphi mode, at least).
It's simply more readable and a shortcut.
>>>
>>> It's definitely the opposite: It is
Jürgen Hestermann schrieb:
> No, it happens with static arrays, if you set pia := @ia, ia[x] and
> pia[x] will give you the same result (in delphi mode, at least).
It's simply more readable and a shortcut.
>>> It's definitely the opposite: It is *less* readable
>> This is your opinio
In our previous episode, J?rgen Hestermann said:
[ Charset ISO-8859-15 unsupported, converting... ]
> >> p
> > The value of a pchar.
>
> What do you mean by "value"? The pointer or the character it is pointing
> to? It seems that p sometimes means the first and sometimes the latter.
The pointer
Jürgen Hestermann wrote:
What has the one thing to do with the other? It would have been easy
to introduce dynamic arrays without hiding away its nature from the user.
Easy, maybe / useful, far less
The beauty of the current solution is that static and dynamic arrays can
be substituted with
C is popular *even though* it is an awful concept.
It is like the video cassettes.
Betamax and Video2000 were the better quality,
but VHS was the most popular cassette.
Yes, sadly this is true (same with Microsoft pressing one awfull OS
after the other into the market). Not always the best win
The beauty of the current solution is that static and dynamic arrays can
be substituted with each other, simple by changing the declaration, and
adding/removing a setlength. All other code can be left as it is.
If you needed the "^" for dyn arrays everywhere, then you would have to
make huge cha
In our previous episode, J?rgen Hestermann said:
> > The beauty of the current solution is that static and dynamic arrays can
> > be substituted with each other, simple by changing the declaration, and
> > adding/removing a setlength. All other code can be left as it is.
> > If you needed the "^"
Jürgen Hestermann wrote:
The beauty of the current solution is that static and dynamic arrays
can be substituted with each other, simple by changing the
declaration, and adding/removing a setlength. All other code can be
left as it is.
If you needed the "^" for dyn arrays everywhere, then you w
2009/10/12 Rainer Stratmann :
> Am Montag, 12. Oktober 2009 11:02 schrieb Jürgen Hestermann:
>> > Remember, Pascal is merely a TEACHING language, unsuitable for commercial
>> > software development, which is why we have C. :)
>>
>> And why should that be the case? What are the outstanding feature
On Mon, 12 Oct 2009 12:49:03 +0200, Jonas Maebe
wrote:
> On 11 Oct 2009, at 18:37, Matthias Klumpp wrote:
>>
>> I decided to use this version of FPC for now. Thank you for your help!
>> But now I have problems to compile the compiler:
>> First I got the error message
>>
>> make[7]: *** No rule to
On Mon, 12 Oct 2009 12:49:03 +0200, Jonas Maebe
wrote:
> On 11 Oct 2009, at 18:37, Matthias Klumpp wrote:
>>
>> I decided to use this version of FPC for now. Thank you for your help!
>> But now I have problems to compile the compiler:
>> First I got the error message
>>
>> make[7]: *** No rule to
Am Montag, 12. Oktober 2009 16:21 schrieb Gustavo Enrique Jimenez:
> 2009/10/12 Rainer Stratmann :
> > Am Montag, 12. Oktober 2009 11:02 schrieb Jürgen Hestermann:
> >> > Remember, Pascal is merely a TEACHING language, unsuitable for
> >> > commercial software development, which is why we have C.
2009/10/12 Marco van de Voort :
> In our previous episode, Jürgen Hestermann said:
>>
>> What is the problem with search-and-replace? If you are forced to change
>> your code you will have a closer look at it and may get aware of side
>> effects of the change.
>
> Yes, and if I had enough time I'd
On Sun, Oct 11, 2009 at 5:25 PM, "Vinzent Höfler"
wrote:
> Andrew Brunner :
>
>> 1st benefit:
>>
>> declaring methods associated with classes before TIntArray needs to be
>> defined or declared.
>> eg. procedure DoSomething(Var Data:TIntArray); vs (DataP:PIntArray);
>
> Huh? Is there any differe
Graeme Geldenhuys wrote:
On 11/10/2009, Andrew Brunner wrote:
FPC forces the ^ operator while accessing structures as pointers.
Delphi didn't force it and I even suspect that memory leaks can result
in NOT using the ^ to denote the reference to the pointer rather than
the pointer itself.
On Mon, Oct 12, 2009 at 12:43 PM, Marc Weustink wrote:
> Graeme Geldenhuys wrote:
>>
>> On 11/10/2009, Andrew Brunner wrote:
>>>
>>> FPC forces the ^ operator while accessing structures as pointers.
>>> Delphi didn't force it and I even suspect that memory leaks can result
>>> in NOT using the
"Jürgen Hestermann" :
> And why should that be the case? What are the outstanding feature of C
> that make it so supperiour? It's illogical and hard to maintain syntax?
Its "Compile anything, crash everywhere." interface. :P
Vinzent.
--
Jetzt kostenlos herunterladen: Internet Explorer 8 und M
"Jürgen Hestermann" :
> Adding yet another variant is not good. I once thought that Pascal was
> superior to other languages because of it's clear and strict concept but
> now there is no longer *the* Pascal language anymore.
If you're searching for some stricter Pascal then maybe you should gi
Martin :
> The beauty of the current solution is that static and dynamic arrays can
> be substituted with each other, simple by changing the declaration, and
> adding/removing a setlength. All other code can be left as it is.
No, because of subtle differences in the handling of "out" parameters
2009/10/12 Andrew Brunner :
>>> pS[2] <<<
>
> Any idea what the compiler option is under Lazarus (that's what I use
> exclusively)?
>
> I get a compiler error when I don't use the ^ operator.
It only works with {$mode delphi} and lazarus uses {$mode objfpc}, i think.
_
The Lazarus team is glad to announce the 0.9.28 release. This release
is based on fpc 2.2.4.
This release can be downloaded from the SourceForge download page:
http://sourceforge.net/projects/lazarus/files/
Highlights / Major changes:
LCL:
*LCL now uses gtk2 as default widgetset on Linux and BSD
Andrew Brunner :
> On Sun, Oct 11, 2009 at 5:25 PM, "Vinzent Höfler"
>
> Read up on forward declarations. The technique of declaring a typed
> pointer to any data structure in FPC and Delphi was that you can use
> it in fields and methods of objects and data structures w/o having to
> actually ha
On 11 Oct 09, at 10:38, Graeme Geldenhuys wrote:
Hi,
.
.
> Anyway to get to my questions, and using the code snippets shown
> below. This code is all based on the code I am porting from
> SpeedPascal. So maybe some strange usage is simply due to the age of
> SpeedPascal etc..
>
>
> --
Hi Everybody,
I need video4linux support for my new project. I tried vfp unit
I found in the contribute units website.
But it seems very outdated. Itried all things menitioned in the
forum, but I'm not able to get the things up. the code is hard
to read and I found not one comment line :(
Thanks
Mattias Gaertner escreveu:
The Lazarus team is glad to announce the 0.9.28 release. This release
is based on fpc 2.2.4.
This release can be downloaded from the SourceForge download page:
http://sourceforge.net/projects/lazarus/files/
Highlights / Major changes:
LCL:
*LCL now uses gtk2 as defau
2009/10/12 Rainer Stratmann :
> Am Montag, 12. Oktober 2009 16:21 schrieb Gustavo Enrique Jimenez:
>> 2009/10/12 Rainer Stratmann :
>> > Am Montag, 12. Oktober 2009 11:02 schrieb Jürgen Hestermann:
>> >> > Remember, Pascal is merely a TEACHING language, unsuitable for
>> >> > commercial software de
49 matches
Mail list logo
