[fpc-devel] Namespaces like URLs
Adem
listmember at letterboxes.org
Tue Jul 27 04:30:20 CEST 2010
On 2010-07-27 5:06 AM, Martin wrote:
>> You would make a notE of that in a cfg file --either a global one, or
>> per project.
> You mean as in a namespace to path translation?
>
> so I write in my cfg
> C:\laz_svn\ = C:\lazarus
> ?
Can we please think out of the box of how you would fit that in the cfg
file for a moment and consider the larger picture?
Yes, in that example, 'laz_svn' would be a central indirection
identifier to your 'C:\lazarus'.
But, it could also contain protocol information (such as ftp etc.) to
accessing a remote machine.
> Then why have the namespace identifiers in the source look like a path
> on disk at all?
Because it is helpful?
But, of course, you don't have to --as long as you devise a way to get
to the path.
> Why not all make them symbolic?
How symbolic you want them would be up to you the user.
> It doesn't have to be a single word like in my other mail thread (so I
> still prefer that) => it could be fpc.core.rtl
>
> Mind if used in "uses foo *in* 'namespace' " => iot's a string, so
> dot, slash you name it, whatever you like
?
>>> will work on a default windows install; not to speak a linux system.
>>> The path depends on the system.
>> Yes. And, as long as you're working on it on a single machine and not
>> intending to move to another machine, that solution is fine.
> Wrong, As I said I have 4 diff installations, and I move stuff between
> them
Of course you can. As long as they are identical where it matters.
I can even set up a 20 installations, even with spaces in paths. All I
have to do is to map the root folder as another disk with a letter.
Trouble is, when I want to use another machine, I need to do pretty much
all of it all over.
>
> See my other thread => I never need to make a change, once I set it up
> => butif the path is in the pascal source, I keep having to change stuff
If you're so comfortable with that, then why are you interested in aliases?
Just because you have 2 file names conflicting?
You know that it's not an impossible problem, don't you?
You just rename at least them and go on living a peaceful life.
IOW, if you boil everything down to how it immediately helps you and
only you, there's little reason to consider alternatives.
More information about the fpc-devel
mailing list