On Mon, 28 Jan 2013, Derek Gaston wrote:
No problem - go for it. Sorry for inserting an abbreviation... not sure why I
did that, I
normally wouldn't!
No worries.
Why the separate VariableGroup::_sys and VariableGroup::sys()?
Shouldn't that get inherited fine from Variable?
---
Roy-
No problem - go for it. Sorry for inserting an abbreviation... not sure
why I did that, I normally wouldn't!
Derek
On Mon, Jan 28, 2013 at 4:45 PM, Roy Stogner wrote:
>
> On Fri, 25 Jan 2013, Derek Gaston wrote:
>
> Would it break everything in the world if I added a pointer to the
>> System
On Fri, 25 Jan 2013, Derek Gaston wrote:
Would it break everything in the world if I added a pointer to the
System the Variable is in to the Variable object? That way from a
Variable you could get the System and from the System you could get
the EquationSystems.
Before people start to depend
Ok - this would simplify things quite a bit... I'll probably do an initial
implementation without it, then add it later and change my implementation.
Derek
On Fri, Jan 25, 2013 at 4:49 PM, Kirk, Benjamin (JSC-EG311) <
benjamin.kir...@nasa.gov> wrote:
> I can't think of anything it would break,
I can't think of anything it would break, so this would be a natural way to go.
We don't support creating variables any other way except though a system, so I
think you are safe.
-Ben
On Jan 25, 2013, at 5:35 PM, "Derek Gaston" wrote:
> All,
>
> I need a unique way to refer to variables.
This might still be a good thing to do... but I figured out that this isn't
necessary for what I'm working on...
Derek
On Fri, Jan 25, 2013 at 4:34 PM, Derek Gaston wrote:
> All,
>
> I need a unique way to refer to variables. I could go with
> EquationSystems Pointer, System name (or number),
All,
I need a unique way to refer to variables. I could go with EquationSystems
Pointer, System name (or number), var name (or number) or something along
those lines... but it makes it cumbersome to do lookup.
I was hoping that the Variable object would help me here... but it doesn't
know about
