Browse, Buffer, Dataset, Frame, Menu, Query, Stream, Temp-Table, Variable, and Work-Table are all things which can be defined as shared.
I have a table which has common information for all shared things.
What collective noun would you use for this set?
SharedElement?
On Mon, Jul 6, 2015 at 10:07 AM, Thomas Mercer-Hursh
wrote:
> Collective Noun
> Thread created by Thomas Mercer-Hursh
>
> Browse, Buffer, Dataset, Frame, Menu, Query, Stream, Temp-Table, Variable,
> and Work-Table are all things which can be defined as shared.
>
> I have a table which has common information for all shared things.
>
> What collective noun would you use for this set?
>
> Stop receiving emails on this subject.
>
> Flag this post as spam/abuse.
--
Tim Kuehn: Senior Consultant - TDK Consulting Services
President - Ontario PUG
Program Committee Chair - PUG Challenge Americas,
Course Instructor: Intro to OO Concepts for Procedural Programmers
Skype: timothy.kuehn
Ph: 519-576-8100
Cell: 519-781-0081
Flag this post as spam/abuse.
Element is a good shout. There's also the wonderfully generic "widget".
SharedThings obviously...
I suppose there are three points I should add.
1. "Shared" includes PUBLIC and PROTECTED since they both make something available outside the compile unit.
2. "Variable" includes PROPERTY ... and, yes, one can tell the difference.
3. Most significantly, I am in the process of adding information on all of these "things" to ABL2DB, whether shared or not. While there is no corresponding table that needs a name, the same name would apply to the process which collects these "things".
Element is doesn't have the connotations of Object, which I had been using, but also doesn't seem to have the right feel.
Widget seems to have a specific meaning which does not correspond to some of these "things".
You lot are so pessimistic. Some more suggestions:
Liability
CarCrash
Quagmire, morass, misery, ruin, PitOfDespair, RoadToHell...
I'd submit "Element" since these shared components are all language
elements. If the varies entities are defined in other places in the
system, then how about
SharedScope
and use it to track pointers to the part of the system which holds the
entity's information.
On Mon, Jul 6, 2015 at 10:29 AM, Thomas Mercer-Hursh
wrote:
> RE: Collective Noun
> Reply by Thomas Mercer-Hursh
>
> I suppose there are three points I should add.
>
> 1. "Shared" includes PUBLIC and PROTECTED since they both make something
> available outside the compile unit.
>
> 2. "Variable" includes PROPERTY ... and, yes, one can tell the difference.
>
> 3. Most significantly, I am in the process of adding information on all of
> these "things" to ABL2DB, whether shared or not. While there is no
> corresponding table that needs a name, the same name would apply to the
> process which collects these "things".
>
> Element is doesn't have the connotations of Object, which I had been using,
> but also doesn't seem to have the right feel.
>
> Widget seems to have a specific meaning which does not correspond to some of
> these "things".
>
> Stop receiving emails on this subject.
>
> Flag this post as spam/abuse.
--
Tim Kuehn: Senior Consultant - TDK Consulting Services
President - Ontario PUG
Program Committee Chair - PUG Challenge Americas,
Course Instructor: Intro to OO Concepts for Procedural Programmers
Skype: timothy.kuehn
Ph: 519-576-8100
Cell: 519-781-0081
For the ones that are shared, my data structure is
CompileUnit<-SharedObject<-SharedVariable->Variable
for non-shared and shared alike, it is
CompileUnit<-Block<-ScopedVariable->Variable.
So, what I am trying to name here is the table currently called SharedObject and the Class which is used to create these structures which has been BuildShared, but now will also be doing the build for non-shared.
Structure?
I suppose there are three points I should add.
1. "Shared" includes PUBLIC and PROTECTED since they both make something available outside the compile unit.
2. "Variable" includes PROPERTY ... and, yes, one can tell the difference.
3. Most significantly, I am in the process of adding information on all of these "things" to ABL2DB, whether shared or not. While there is no corresponding table that needs a name, the same name would apply to the process which collects these "things".
Element is doesn't have the connotations of Object, which I had been using, but also doesn't seem to have the right feel.
Widget seems to have a specific meaning which does not correspond to some of these "things".
Flag this post as spam/abuse.
What he said....
On Mon, Jul 6, 2015 at 11:06 AM, Peter Judge
wrote:
> RE: Collective Noun
> Reply by Peter Judge
> I'd be careful of using 'shared' to include those. 'Shared' has a specific
> meaning in ABL to most (all?) programmers.
>
>
>
>[collapse] From: Thomas Mercer-Hursh [mailto:bounce-tamhas@community.progress.com]
> Sent: Monday, 06 July, 2015 10:30
> To: TU.OE.Development@community.progress.com
> Subject: RE: [Technical Users - OE Development] Collective Noun
>
> RE: Collective Noun
> Reply by Thomas Mercer-Hursh
>
> I suppose there are three points I should add.
>
> 1. "Shared" includes PUBLIC and PROTECTED since they both make something
> available outside the compile unit.
>
> 2. "Variable" includes PROPERTY ... and, yes, one can tell the difference.
>
> 3. Most significantly, I am in the process of adding information on all of
> these "things" to ABL2DB, whether shared or not. While there is no
> corresponding table that needs a name, the same name would apply to the
> process which collects these "things".
>
> Element is doesn't have the connotations of Object, which I had been using,
> but also doesn't seem to have the right feel.
>
> Widget seems to have a specific meaning which does not correspond to some of
> these "things".
>
> Stop receiving emails on this subject.
>
> Flag this post as spam/abuse.
>
> Stop receiving emails on this subject.
>
> Flag this post as spam/abuse.
--
Tim Kuehn: Senior Consultant - TDK Consulting Services
President - Ontario PUG
Program Committee Chair - PUG Challenge Americas,
Course Instructor: Intro to OO Concepts for Procedural Programmers
Skype: timothy.kuehn
Ph: 519-576-8100
Cell: 519-781-0081[/collapse]
Structs are something I wish we had.
All the variants of shared are clearly distinguished and I see little potential for confusion since, remember that these are all relevant to the compile unit, so one starts off knowing whether it is a class or not.
If one were not going to call it SharedObject or SharedElement, what would one call it? Public seems to have connotations in the other direction.
PUBLIC and PROTECTED should go somewhere else and be differentiated
from old SHARED variables.
On Mon, Jul 6, 2015 at 11:14 AM, Thomas Mercer-Hursh
wrote:
> RE: Collective Noun
> Reply by Thomas Mercer-Hursh
>
> Structs are something I wish we had.
>
> All the variants of shared are clearly distinguished and I see little
> potential for confusion since, remember that these are all relevant to the
> compile unit, so one starts off knowing whether it is a class or not.
>
> Stop receiving emails on this subject.
>
> Flag this post as spam/abuse.
--
Tim Kuehn: Senior Consultant - TDK Consulting Services
President - Ontario PUG
Program Committee Chair - PUG Challenge Americas,
Course Instructor: Intro to OO Concepts for Procedural Programmers
Skype: timothy.kuehn
Ph: 519-576-8100
Cell: 519-781-0081
Why? What properties do they have that would require a separate table, non-overlapping with shared?
FWIW, Proparse thinks in terms of imported and exported. Shared is imported; new shared is exported.
SharedDeclaration?
Declaration is interesting .... fwiw, one of the "discoveries" in the process of working on this is that not everything comes into existence through a DEFINE. Parameters are an example of an implied definition.