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 from Delphi, I
guess. Isn't this a potential
2010/1/31 Paul van Helden p...@planetgis.co.za:
But it is things like this that trip up people coming from Delphi, I guess.
Isn't this a potential improvement to the compiler though: scan for
overloaded functions before assuming that it is the result value (like
Delphi does)? (Or warn about
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
On 2010/01/31 10:30 AM, Daniël Mantione wrote:
This behaviour is intentional to allow you to read instead of just
write the function result. The incompatibility just affects recursive
procedures without parameters, which seldomly occurs, because normally
the parameters determine the
In our previous episode, Paul van Helden said:
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 from Delphi, I
guess. Isn't
Thanks, I just added the exit 0 to the script. I can execute the
script and it does what it is supposed to do. I just can't get the
script to run before I build via Lazarus. No matter what I do I keep
seeing the error 127. Any other ideas?
TExternalToolList.Run Exception: the process exited
On 31 Jan 2010, at 05:07, Andrew Brunner wrote:
This script is set as executable and the permissions were incorrect at
first but Lazarus knew to throw me the error. I fixed the permissions
but get an error 127 on building the project. I tried ./prebuild.sh
and just prebuild.sh and the full
On Sun, 31 Jan 2010 14:16:10 -0600
Andrew Brunner andrew.t.brun...@gmail.com wrote:
No matter what I do I keep
seeing the error 127. Any other ideas?
If the path to the file is wrong you get that error.
Use a full path to the file and make sure you set the execute flag.
Wonderful. It's working now. Thanks guys.
On Sun, Jan 31, 2010 at 2:30 PM, Jonas Maebe jonas.ma...@elis.ugent.be wrote:
On 31 Jan 2010, at 05:07, Andrew Brunner wrote:
This script is set as executable and the permissions were incorrect at
first but Lazarus knew to throw me the error. I
Hello, FPC developers' list.
Is there a reason that during project compilation compiler duplicates
all the resource files in the compiler output dir? For me it looks as
both a waste of time and hdd free size. This happens for all LFM and RES
files which my project includes.
--
Best regards,
Paul van Helden wrote:
And to regain my productivity: to figure out how to debug with Lazarus
the way I'm used to in Delphi...
I miss this too, though recently there was a lot of improvements to
debugging support. All I can say is, be thankful you didn't start 5 years
ago with FPC where
Hello, FPC developers
Any hints on these bugs?
http://bugs.freepascal.org/view.php?id=12923
http://bugs.freepascal.org/view.php?id=15642 // patch proposed to
workaround RTL limitation in LCL
This is mostly concern of Windows OS. Moders Unix doesn't have the
problem, usually having UTF8 as
Il 01/02/2010 04:09, Paul Ishenin ha scritto:
Hello, FPC developers' list.
Is there a reason that during project compilation compiler duplicates
all the resource files in the compiler output dir? For me it looks as
both a waste of time and hdd free size. This happens for all LFM and RES
files
01.02.2010 14:50, Giulio Bernardi wrote:
The reason is explained in this log message (2008-01-10):
* .res files must be copied to units output folder, otherwise .res files
will not be found when only compiled units path is available and
compiler does not know anything about sources folder.
14 matches
Mail list logo
