ecl

Your data is in a good form to get into a dataframe with the right indices.

It's not exactly clear. The spec says:

Executes forms in a dynamic environment where the indicated handler bindings are in effect.

and then says

If an appropriate type is found, the associated handler is run in a dynamic environment where none of these handler bindings are visible (to avoid recursive errors).

If you interpret "run" meaning to call the function, that suggests that the handler expressions are evaluted once, when the bindings are made. This is the CCL/ABCL/ECL/LispWorks implementation, so state is maintained in the closure.

But SBCL appears to have intepreted "run" as meaning "evaluated and called". So a new closure is created each time the handler is run, and state is lost.

I suspect the intent was the first interpretation, since CL has no other "lazy" bindings.

If you change the code in the question to this:

Try logging the SQL query, instead of the values. This should help you see what you're actually telling the DBMS to do. You may find that you're sending it the wrong values.

Also, instead of a couple of numerical for loops, try this:

I'm pretty sure ECL simply does not support general unicode filenames on Unix or Linux, however they get encoded in the underlying filesystem (I also don't know how that happens with *nix nowadays, although I guess there must be a standard now).

The specific error you're seeing originates here, in pathname.d. If you then look in unixfsys.d you'll see that ECL_NAMESTRING_FORCE_BASE_STRING is one of the flags passed to ecl_namestring all over the place, and this isn't conditionalized by anything.

So at the very least you would need to compile ECL from scratch, and more probably it simply does not support general unicode filenames at all.

but the problem is that line if line[:3] == 'cid': continue seems to be working only 'sometimes'(however strange it might sound), and I want to have file like above, but without any cid:value fields.

Seems to be working in every case to me. The issue is that your script only checks if 'cid' is the first three characters of the input line.

In the demonstration input you provide, cid is only the start of the line in one case (which is excluded from the output), in every other case it's in the middle of the input line and thus never going to match anything.

If you want to exclude every cid entry, you need to do so on the entries (the inner loop after the split) e.g.

Try this -

The reason why you get the warning is because str_detect is vectorised function meaning 1st value in col is matched with 1st value of fields, 2nd value with the 2nd and so on. Length of col is 5 and length of fields is 7 so their lengths are incompatible and that is what the warning is saying.

To filter the rows in data where each value of fields is present in base R, you could do :

You can dict comprehension it easily: