You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I realized the problem lies with the unicode characters that are at the beginning or end of each cell. will cause field_start and field_length calculations to be incorrect.
The temporary way I came up with is to use a variable that defines the boundary:
const BOOL checkboundary(char x) {
return x == '\t' || x == ',';
};
const auto& isbeginend = data_pos == 0 || (data_pos > 1 &&
((!checkboundary(this->data_ptr->data[data_pos]) && checkboundary(this->data_ptr->data[data_pos - 1])) ||
(!checkboundary(this->data_ptr->data[data_pos]) && data_pos < size - 1 && checkboundary(this->data_ptr->data[data_pos + 1]))));
From there recalculate the flag:
const auto& flag = compound_parse_flag(in[data_pos], isbeginend);
It may work in some cases but not completely. B.TXT
Hi,
Please check the attached file.
The separator character is tab.
The third column header returns the wrong content.
Thanks you.
B.TXT
The text was updated successfully, but these errors were encountered: