I'm just curious, does there exist descriptions for the various SVN
branches (purpose, maintainer, state)?
Florian has offered me an new branch, for my parser etc. projects, but
he seems to be very busy right now. So I'll present a roadmap of my
activities, all around the parser and compiler:
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 wonder why FPC allows
to use it everywhere?
IMO the filespec should allow for
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
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
On 11 Jul 2010, at 15:47, Hans-Peter Diettrich 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,
That is incorrect. Relative
11.07.2010 17:47, Hans-Peter Diettrich:
I know that the in filespec is part of the Delphi syntax, but what
is it really good for?
For specifying path.
This way you are able to prevent any ambiguity in which file will
actually be selected. Not sure how exactly this is implemented in FPC,
but
On 11 Jul 2010, at 15:29, Hans-Peter Diettrich wrote:
I'm just curious, does there exist descriptions for the various SVN branches
(purpose, maintainer, state)?
The commit messages (mainly the initial one).
The stand-alone preprocessor code ($PreprocWrite, commandline option -m) does
not
Am 11.07.2010 um 19:48 schrieb Daniël Mantione:
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
Jonas Maebe schrieb:
AFAIK it's not allowed to rename units this way, and since
(currently) only absolute filenames are implemented,
That is incorrect. Relative file names do work. They are resolved
relative to the current working directory of the compiler.
So what's the current working
On 11 Jul 2010, at 23:55, Hans-Peter Diettrich wrote:
Jonas Maebe schrieb:
AFAIK it's not allowed to rename units this way, and since
(currently) only absolute filenames are implemented,
That is incorrect. Relative file names do work. They are resolved
relative to the current working
On Wed, Jul 7, 2010 at 8:39 AM, Marc Weustink marc.weust...@cuperus.nl
wrote:
Since my fileserver exports the shares to both nfs and samba, I use nfs for
linux/osx, and samba for windows.
I faintly remember that I might have had some issues with samba on OSX, so I
quit that exercise (since
Jonas Maebe schrieb:
The stand-alone preprocessor code ($PreprocWrite, commandline
option -m) does not compile since a long time. I could it make work
again, and already supplied the according patch in Mantis.
And as I replied in mantis two days ago, a) that option is not
documented in the
Jonas Maebe schrieb:
That is incorrect. Relative file names do work. They are resolved
relative to the current working directory of the compiler.
So what's the current working directory?
The current directory when the compiler was started. E.g.:
c:\pp\src ppc386 project\test.pas
-
13 matches
Mail list logo
