Ali Somay

After fiddling with it for few days, I have the picture of Max C API in my mind. 

What I find absence in the docs, and SDK is the .h files of individual objects.

I was in a situation where I wanted to get the associated symbol with a coll object.

It seems impossible to reach an object's internal storage without having a definition of its type. 

So in this case I was fortunate enough to obtain "coll.h" and the type "t_coll" was defined there so I could get this data.

But what if I would like to get the associated name with a send |send foo| or the arguments of a select object |select foo bar| ?

Then probably I need the precise info about how they defined internally, probably I would need a fictional "select.h" and "send.h".

At least this is how I understand it by now.

Is there a reason this functionality is not accessible to external developers ? 

After fiddling with it for few days, I have the picture of Max C API in my mind. 

What I find absence in the docs, and SDK is the .h files of individual objects.
I was in a situation where I wanted to get the associated symbol with a coll object.
| coll foo |, get the symbol "foo" here. 

It seems impossible to reach an object's internal storage without having a definition of its type. 
So in this case I was fortunate enough to obtain "coll.h" and the type "t_coll" was defined there so I could get this data.
But what if I would like to get the associated name with a send |send foo| or the arguments of a select object |select foo bar|  ?
Then probably I need the precise info about how they defined internally, probably I would need a fictional "select.h" and "send.h".

At least this is how I understand it by now. 

What are your thoughts in this ? 
Is there a reason this functionality is not accessible to external developers ? 

All the best. 

After fiddling with it for few days, I have the picture of Max C API in my mind. 

What I find absence in the docs, and SDK is the .h files 

Open question about the SDK