fo | experimental language which adds functional programming | Functional Programming library

The online help page of seqplot (of which seqdplot is an alias for type="d") states

A State distribution plot (type="d") represents the sequence of the cross-sectional state frequencies by position (time point) computed by the seqstatd function and rendered with the plot.stslist.statd method. Such plots are also known as chronograms.

So you get the data used by seqdplot with function seqstatd. Actually, the distributions are in the attribute Frequencies.

Your sample data contains only three sequences of length 10 with a single spell in state 'OT'. I stored it in s.spl

If I correctly understood your issue, you want to be able to open a "parent" without opening its children.

But then, why did you write your code to do so ?

See the culprit in the code bellow:

You might get better results from switching the conditional from == to in. That way if the line you are testing has any leading characters it will still pass the condition. For example below I changed the x=='-----...' to '-----' in x. the change is at the very end of the long string of hyphens.

Please try the following XSLT.

Input XML

Try it. It Will be work. Take out the choice of the name of the animation in a separate property.

Even though nobody posted an answer, from the comment section I could conclude that:

• Nobody found any undefined behavior in the bug repro code.
• At least some of you were able to reproduce the undesired behavior.

So I filed a bug report against Visual Studio 2019.

The Microsoft team confirmed the problem.

However, unfortunately it seems like Visual Studio 2019 will not receive a bug fix because Visual Studio 2022 seemingly does not have the bug. Apparently, the most recent version not having that particular bug is good enough for Microsoft's quality standards.

I find this disappointing because I think that the correctness of a compiler is essential and Visual Studio 2022 has just been released with new features and therefore probably contains new bugs. So there is no real "stable version" (one is cutting edge, the other one doesn't get bug fixes). But I guess we have to live with that or choose a different, more stable compiler.

According to man7.org getifaddrs, any of the socket operations could be a cause for EBADF

ERRORS

getifaddrs() may fail and set errno for any of the errors specified for socket(2), bind(2), getsockname(2), recvmsg(2), sendto(2), malloc(3), or realloc(3).

Unrelated, but do you do freeifaddrs() somewhere?

The int record_compare_field_1(); declaration does not have a prototype. This is an obsolescent feature of the C17/C18 standard.

In the function call qsort(database, 5, sizeof(Record), record_compare_field_1);, the record_compare_field_1 argument has type int (*)() and qsort's compar parameter has type int (*)(const void *, const void *). This is allowed by this rule from C17 6.2.7:

— If only one type is a function type with a parameter type list (a function prototype), the composite type is a function prototype with the parameter type list.

The actual record_compare_field_1 function definition has the prototype int record_compare_field_1(Record, Record) where the Record type is defined by typedef char Record[3][8]. Since array parameters are adjusted to pointers, this is the same as the prototype int record_compare_field_1(char (*)[8], char (*)[8]).

qsort will call the passed in record_compare_field_1 function with the wrong prototype, leading to undefined behavior. Most C implementations use the same representation for all object pointer types, so it lets you get away with it.

To do it properly, the record_compare_field_1 function could be defined like this:

Judging from the usage of the rename command in the second code, you seem to have the perl-based rename command available. (There are two different rename commands, one is perl-based, the other is not. Confusing.)
Then you can rename the files removing the double quotes just with: