[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [GT] alias resolution ... sub resolve_alias revisited



RAS,

I think your suggestions is a good one. I think we can agree on the
syntax for alias as follows:

Aliases::Global::<alias_name> <full_system_name>
Where
<alias_name> is a string of characters, not including a ":". We could be
stricter, limiting it to alphanumeric and underscore.

This will also work with the "object aliases" (the ones where you need
to use "@" to invoke). Note that object aliases have the form
<kind>::<alias_name> or
<kind>:<alias_name>
(e.g., I:MyRSI).

I'd say go with that version.

There is an awkwardness with aliases:
- aliases standing for full system names are just used as is
- object aliases (i.e., aliases for indicators, signals, etc., need to
  Be prefixed with "@").

I'd like to see whether it is possible to drop that "@".

Th.


> -----Original Message-----
> From: Robert A. Schmied [mailto:ras
AT
acm.org]
> Sent: Thursday, May 01, 2008 4:43 PM
> To: devel
AT
geniustrader.org
> Subject: Re: [GT] alias resolution ... sub resolve_alias revisited
> 
> 
>     while ($sysname !~ /:/) {
> 
> of course the pattern /:/ requires that an alias NOT contain a colon,
> but
> i think that is probably acceptable -- is there anywhere a
> specification
> for what an alias might have to be or must not be? backtest.pl had the
> most description, Tools.pm discussed @ based aliases some, maybe some
> more about aliases on the web pages?