Android Question What is the best way to return an structure of values from a class?

[davepamn]

Should I use a type of return a list of values from a class or should I use a map?

 

[Roycefer]

It depends on the details and needs of your program. If you plan on iterating through the results, a List will be better. You can iterate through the values of a Map but they won't necessarily be in the same order in which you put them in the Map. If you want to be able to access the values using a key/value pattern where key is not just an integer, then obviously a Map will be better.

You can also create a custom Type whose fields contain all your info and return an instance of that Type.

 

[davepamn]

The type worked.

I put the type in the class. However, it seems like that is a strange place to put the type because it is difficult to find logically

 

[derez]

You can see an example here https://www.b4x.com/android/forum/threads/class-treeview-class-tree-and-node.19082/
There is a type "Data" which is defined at tree class and used in main (to fill data requested by tree).
It makes sense since this type is used by the tree class and should be part of it. If someone wants to copy the class for use in another application - there it is already.

 

[davepamn]

Usually "data types" are kept in a header file or a specification module. I want to organize the "type" structure in a best practice manner.

 

[derez]

You can define it in the Process_Globals of the main or a code module.

 

[SteveTerrell]

Usually "data types" are kept in a header file or a specification module. I want to organize the "type" structure in a best practice manner.

A C type #include "header file path and name" would be helpful where the same types or constants are used in several projects. This way only one file needs to be maintained.

 

[davepamn]

You can define it in the Process_Globals of the main or a code module.

Putting the Database class object in a process_globals section of the module worked great.

 

[MaFu]

A C type #include "header file path and name" would be helpful where the same types or constants are used in several projects. This way only one file needs to be maintained.

Put it in a code module Process_Globals and save this file in your "Shared Modules" folder. Then you have only one file using everywhere.

 

[LucaMs]

Usually "data types" are kept in a header file or a specification module. I want to organize the "type" structure in a best practice manner.

Create a class for that "data type"