Thread-safe entry-points

[rlaveaux]

Please make the following entry-points thread-safe:

• EX_ALERT
• EX_CALL_BY_PROCID
• EX_CONVERT_CHARSET_TO_CHARSET
• EX_COUNT_FIELDS
• EX_COUNT_INVISIBLE_FIELDS_TOO
• EX_COUNT_TABLES
• EX_CREATE_PICTURE
• EX_CURRENT_PROCESS_NUMBER
• EX_DISPOSE_PICTURE
• EX_DUPLICATE_PICTURE
• EX_EXECUTE_FUNCTION
• EX_EXECUTE_METHOD
• EX_FIELD_ATTRIBUTES
• EX_FREEZE_PROCESS
• EX_GET_4D_FOLDER
• EX_GET_FIELD
• EX_GET_FIELD_RELATIONS
• EX_GET_METHOD_ID
• EX_GET_PICTURE_DATA
• EX_GET_PRINT_INFO
• EX_GET_PROCESS_INFO
• EX_GET_STRUCTURE_FULLPATH
• EX_GET_TABLE_FIELD_NUMBER
• EX_GET_TABLE_NAME
• EX_GET_VARIABLE
• EX_NB_PROCESS
• EX_NEW_PROCESS
• EX_PUT_PROCESS_TO_SLEEP
• EX_RECORD_NUMBER
• EX_SET_FIELD
• EX_SET_VARIABLE
• EX_YIELD
• EX_YIELD_ABSOLUTE

[miyako]

Those 3 have been threadSafe for quite some time

see https://github.com/4d/4D-Plugin-SDK/blob/master/4D%20Plugin%20API/EntryPoints.h

[desoi]

I would like to have these entry points become thread safe:

• EX_GET_PACKED_RECORD
• EX_SET_PACKED_RECORD

[rlaveaux]

Thank you for the update. Unfortunately, the following entry points are still not thread-safe:

• EX_CALL_BY_PROCID
• EX_EXECUTE_FUNCTION
• EX_EXECUTE_METHOD
• EX_GET_FIELD_RELATIONS
• EX_GET_METHOD_ID
• EX_RECORD_NUMBER
• EX_SET_FIELD
• EX_SET_VARIABLE

Please understand that this really limits me to making my plugins thread-safe. So far I have prepared 4 plugins for multi-threading, but because of these limitations, I can not test them.

[rlaveaux]

I just checked again. The following entry-points are still outstanding:

• EX_CALL_BY_PROCID
• EX_COUNT_FIELDS
• EX_COUNT_INVISIBLE_FIELDS_TOO
• EX_COUNT_TABLES
• EX_EXECUTE_FUNCTION
• EX_EXECUTE_METHOD
• EX_FIELD_ATTRIBUTES
• EX_GET_FIELD
• EX_GET_FIELD_RELATIONS
• EX_GET_TABLE_FIELD_NUMBER
• EX_GET_TABLE_NAME
• EX_GET_VARIABLE
• EX_RECORD_NUMBER
• EX_SET_FIELD
• EX_SET_VARIABLE

Can I please get a status update what to expect and when?

[heubachmedia]

I would add:

• EX_RECORDS_IN_SELECTION

How is the status (also with EX_GET_VARIABLE and EX_GET_FIELD)? Our customers would like to execute our plugin in pre-emptive mode.

[rlaveaux]

How is the status (also with EX_GET_VARIABLE and EX_GET_FIELD)? Our customers would like to execute our plugin in pre-emptive mode.

Hi Christian, I believe we can conclude that these points will not be addressed.

Regarding EX_RECORDS_IN_SELECTION, you can use PA_ExecuteCommand as a replacement to call the "Records in selection" function. Regarding EX_GET_VARIABLE and EX_GET_FIELD, I was told to use EX_GET_POINTER_VALUE instead, since it's thread-safe.

I have rewritten some parts of the plugin SDK to use these entry-points instead. I will see if I can do a pull request with my changes.