[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [GT] trunk/GT/Tools.pm 2008-03-30 04:07:51 UTC (rev 594) or later
Hmmm... There should be no changes at all to object aliases (unless one
wants to take out the "@", but that is just a proposed patch, and I am
not sure whether it is a good idea or not).
What I did with the object aliases is the following:
1. Removed the hard wired locations for the various paths to a common
location and allow configuration in options file. In the existing
system, the code hardwired in /usr/share/geniustrader/aliases which is a
no-no.
2. These aliases are loaded everytime an object alias is evaluated. This
is not necessary. A single load at conf load time is sufficient.
None of these should have a visible effect on the user (other than that
a common location should be defined in the options file, as all other
configuration for GT is).
Regarding the foreach (@options)..., I think this is a really useful
feature. Basically, it allows the script to override settings in the
options file. This is no different from editing the options file and
then running the script, and then editing the option file back to how it
was. You often run into situations that you might want to run analysis
over different input directories, for example. This is a simple way to
do so. E.g., say you have data in different input formats, you can now
run gt without having to change the options file all the time.
This code was in one of the scripts, and is now available in all... I
have been using this extensively...
Th.
P.S. Your improvements to alias resolution are not in the repository
yet, by the way...
> -----Original Message-----
> From: Robert A. Schmied [mailto:ras
AT
acm.org]
> Sent: Saturday, May 03, 2008 12:21 PM
> To: devel
AT
geniustrader.org
> Subject: Re: [GT] trunk/GT/Tools.pm 2008-03-30 04:07:51 UTC (rev 594)
> or later
>
> i'm still unsure why you felt it necessary to clobber the object
> aliases as hard as you did. but i haven't evaluated it at all yet.
>
> and i don't know what unintended consequence(s)
> foreach (@options) {
> my ($key, $value) = split (/=/, $_);
> GT::Conf::set($key, $value);
> }
> is going to have in the scripts
>
- References:
- [GT] trunk/GT/Tools.pm 2008-03-30 04:07:51 UTC (rev 594) or later, Robert A. Schmied (2008/04/29)
- RE: [GT] trunk/GT/Tools.pm 2008-03-30 04:07:51 UTC (rev 594) or later, Weigert, Thomas (2008/05/03)
- Re: [GT] trunk/GT/Tools.pm 2008-03-30 04:07:51 UTC (rev 594) or later, Robert A. Schmied (2008/05/03)
- RE: [GT] trunk/GT/Tools.pm 2008-03-30 04:07:51 UTC (rev 594) or later, Weigert, Thomas (2008/05/03)
- Re: [GT] trunk/GT/Tools.pm 2008-03-30 04:07:51 UTC (rev 594) or later, Robert A. Schmied (2008/05/03)
- RE: [GT] trunk/GT/Tools.pm 2008-03-30 04:07:51 UTC (rev 594) or later, Weigert, Thomas (2008/05/03)
- Re: [GT] trunk/GT/Tools.pm 2008-03-30 04:07:51 UTC (rev 594) or later, Robert A. Schmied (2008/05/03)