Why use Data Log File Ref as GOOP class reference?

[Phil Duncan]

Hello fellow LVers.

I have been reading a lot about GOOP and it's many implementations from llb's to dqGOOP and Endevo's GOOP wizard that incorporates inheritance. Before I embrace GOOP with gusto I want to understand it completely so that I can implement OOP techniques intelligently and appropriately.

During my investigations I noticed that most GOOP techniques use a typedef enum control dropped into a data log file reference to form the class (object) reference.

I am just wondering why use a datalog file ref? What makes it the preferred option over any other reference type?

Beers and Cheers.

Phil :beer:

[Jeffrey Habets]

During my investigations I noticed that most GOOP techniques use a typedef enum control dropped into a data log file reference to form the class (object) reference.

I am just wondering why use a datalog file ref? What makes it the preferred option over any other reference type?

I guess the most important reason is that with this technique you can create unique references for each class. This way you won't be able to wire ClassA:Method1() to a reference returned by ClassB:Create().

[didierj]

I am just wondering why use a datalog file ref? What makes it the preferred option over any other reference type?

Most probably because NI began this way in the ini-file library.

[crelf]

I am just wondering why use a datalog file ref? What makes it the preferred option over any other reference type?

Because we can The enum dropped into the datalog file ref gives us a really easy way of creating our own reference types. Why is that important? Each class you create should have a different reference type for a number of reasons, including breaking code when you try to use a method from one class on the reference of another. At the programming level, it separates between classes, which, at the lower level, in essence differentiates between the object repositories.

Beers and Cheers.

Phil :beer:

Please have a schooey or two for me (I know you'll comply )

[Phil Duncan]

Thanks for the responses. The data log file refnum makes sense as the best choice now.

The enum dropped into the datalog file ref gives us a really easy way of creating our own reference types.

I did a little investigation (3 mins worth) and the data log file refnum is the only one I found that requires/allows a type cast when created, much like a cluster or array container.

Please have a schooey or two for me (I know you'll comply )

Done and done! ... and done and done and done...

[crelf]

Done and done! ... and done and done and done...

I'd do anything for a Tooheys Old right now...

[Phil Duncan]

I'd do anything for a Tooheys Old right now...

Well here's a teaser for your troubles..

[crelf]

Well here's a teaser for your troubles..

You're lucky there's a swear filter on LAVA...

[Yair]

You're lucky there's a swear filter on LAVA...

I believe the premium members are not subject to this filter, so you can vocalize your discontent.

Just let me get out of the way first...

[crelf]

Just let me get out of the way first...

.

.

.

You can always tell when an Aussie is really really upset - he goes very very quiet...

[didierj]

You can always tell when an Aussie is really really upset - he goes very very quiet...

Something for your next goop project that will always remind you your LAVA-mates: :laugh:

Download File:post-253-1150352215.ctl

[crelf]

Something for your next goop project that will always remind you your LAVA-mates: :laugh:

Why must you all mock me so?

[didierj]

Why must you all mock me so?

Because now it's 4:30 pm, about 30