What ExtendScript extension data types are most compatible with Adobe plugins?

[Premiopolis]

Can an Adobe plugin simply & easily receive ExtendScript datatypes other than numbers & booleans?

I believe strings sent from from panel (ExtendScript) to plugin (C++) are a little clumsy?

What about JS arrays and JSON objects? What do they look like in the C++ context?

So far I've only seen errors when trying to send.

[Bruce Bullis]

> Can an Adobe plugin simply & easily receive ExtendScript datatypes other than numbers & booleans?

No.

> I believe strings sent from from panel (ExtendScript) to plugin (C++) are a little clumsy?

Works great for standard data types. 

> What about JS arrays and JSON objects? What do they look like in the C++ context?

Undifferentiated blobs of data. 

[Premiopolis]

"Undifferentiated blobs of data" - I think some of the 1960s Star Trek episodes features those in starring roles.

So booleans, numbers, and even strings -- strings are relatively straightforward on the plugin side?

[Bruce Bullis · Accepted solution]

You'd have to ask the plug-in developer; strings can get Complicated™. The ExtendScript API allows for getting and setting most data types used as effect parameters.

[Premiopolis]

Developer says it's a little complicated, but he has a plan.  I was hoping for a way to make his life easier.