csvexport troublesome when 'name' field contains commas

[ni-balexand]

I'm using Tracy 0.11.1 on Windows / MSVC.

I've run into an issue that arises when the name of my function contains a comma. This will happen if ZoneScoped is used from a method in a class that has two template parameters, such as: namespace::ClassName<TemplateParamA,TemplateParamB>::methodName

Some potential workarounds:

• Detect < when parsing the output of csvexport, and don't let commas separate the fields until a closing > is found
• If only the first field potentially has a comma, a parser could potentially start with the last comma in the line and work backwards.
• Use ZoneScopedN and pass a name that doesn't have commas

Hypothetically, the file path could also have a comma? Seems unlikely and weird, but that would derail any of those workarounds.

CSV conventions exist for this problem. Fields which contain a comma should be surrounded in double-quote characters, literal double-quote characters should be escaped using two double-quote characters. Unfortunately, this complicates what ought to be a dead-simple format.

Another solution could be to replace commas with something else, like a space, a colon, or some other special character before dumping to CSV.

Or, promote the usage of tab-separated values instead.

[ni-balexand]

Just after publishing the issue, I found out that you can instruct the csvexport program to use a tab character as a separator using the -s option. Passing that from a shell (especially CMD) might be awkward, but it works somewhat seamlessly when invoking it from Python:

csv_export_program_args = [csv_export_program_path, "-s", "\t", str(tracy_file_path)]
csv_export_program_proc = subprocess.Popen(csv_export_program_args, stdout=PIPE)
(csv_data_raw, _) = csv_export_program_proc.communicate(timeout=120)