• Topics with a SQL keyword as name cannot be created


• 
  QueryCondition expressions cannot refer to datafields with SQL keyword as name
  


• 
  ContentFilteredTopic expressions cannot refer to datafields with SQL keyword as name
  

            struct TestStruct;



            struct TestStruct{

                long x;

                TestStruct someEnum;

                string val;

            };

            

            struct TestStruct;



            struct TestStruct1{

                TestStruct y;

            };



            struct TestStruct{

                long x;

            };

            

            struct TestStruct;



            struct TestStruct1{

                TestStruct y;

            };



            struct TestStruct{

                TestStruct1 x;

            };

            

module example {

    typedef sequence NameList;



    struct DataType {

        sequence  nameLists;

    };

};

• 
  Configuring REPLACE as policy on both sides.
  


• 
  Combining REPLACE as policy on one side and MERGE on the other side.
  


• 
  Combining REPLACE as policy on one side and DELETE on the other side.
  


• 
  Combining DELETE as policy on one side and MERGE on the other side.
  

DDS::Duration_t globalStruct = DDS::DURATION_INFINITE;

const DDS::Duration_t globalStructC = DDS::DURATION_INFINITE;

void main(void)

{

    const DDS::Duration_t localStructC = DDS::DURATION_INFINITE;

    DDS::Duration_t copy_localStructC  = localStructC;

    DDS::Duration_t copy_globalStructC = globalStructC;

    DDS::Duration_t copy_globalStruct  = globalStruct;

}

            

const DDS::Duration_t globalStructC = {DURATION_INFINITE_SEC, DURATION_INFINITE_NSEC};

            

• MATLAB is run from a Linux system,


• the OSPL_URI environment variable refers to a Single Process configuration of Open Splice,


• the MATLAB instance has connected to OpenSplice via the Vortex DDS Block Set for Simulink.


• The segmentation fault is reported because Open Splice installs exit handler that gets unloaded from memory before it is called. On Linux systems, the exit handler does nothing. Other MATLAB threads appear to continue to shutdown normally.

• here is no impact on system integrity or MATLAB


• each MATLAB exit can produce a file in the user's home directory starting with 'matlab_crash_dump'. These files can safely be deleted to reclaim disk space.

typedef sequence walk;

struct Adventurer {

    long id;

    walk favourite_walk;

    sequence recent_walks;

};

            

typedef sequence walk;

typedef sequence<sequence, 50> walk_seq;

struct Adventurer {

    long id;

    walk favourite_walk;

    walk_seq recent_walks;

};

            

sequence[0].array[0] = 0

sequence[0].array[1] = 1

sequence[1].array[0] = 10

sequence[1].array[1] = 11

            

sequence[0].array[0] = 0

sequence[0].array[1] = 1

sequence[1].array[0] = 10

sequence[1].array[1] = 11

sequence[2].array[0] = 0

sequence[2].array[1] = 0

            

int[][] array2D = new int [2][3];

array2D[0][0] = 0;

array2D[0][1] = 1;

array2D[0][2] = 2;

array2D[1][0] = 3;

array2D[1][1] = 4;

array2D[1][2] = 5;

            

array2D[0][0]: 0

array2D[0][1]: 3

array2D[0][2]:

array2D[1][0]: 1

array2D[1][1]: 4

array2D[1][2]:

            

send test_SimpleCollectionTopic (

    b_seq => abc

);



check test_SimpleCollectionTopic (

    b_seq=> abc

);