Code annotations for C/C++ not working as expected (by me)

[uwezi]

Description

Quarto version 1.8.25 on Windows 11

I found the closed issue #5060 "Code Annotation for C/C++ & VHDL not handled correctly" when experimenting with Quarto for the very first time. My goal is to include plain C code in my presentation and the annotation feature just looks great.

However using the standard inline comment style in C // is not recognized by the preview and revealjs renderer. It is recognized correctly for C++ code though, here is an example

---
title: "Quarto Basics"
format:
  html:
    code-fold: true
jupyter: python3
code-annotations: hover
---

## C code

```c
#include <avr/io.h> // <1>
int main(void)      // <2>
{
    while (1)       // <3>
    {               // <3>
                    // <3>
    }               // <3>
}
```
1. pre-processor library include
2. main function
3. infinite main loop

## C++ code

```cpp
#include <avr/io.h> // <1>
int main(void)      // <2>
{
    while (1)       // <3>
    {               // <3>
                    // <3>
    }               // <3>
}
```
1. pre-processor library include
2. main function
3. infinite main loop

the revealjs output as screenshots:

However the PDF output shows a different appearance: now the comments have been replaced in both code examples, but the ordered list for the C-code example has not been modified:

[mcanouil]

The standard Inline comment symbol in C is not //. It is only in ANSI C C99 and later.

Quarto uses /* ... */:

• quarto-cli/src/resources/filters/modules/constants.lua

  Line 84 in b89d353

  c = {"/*", "*/"},

---
format: html
code-annottions: true
---

```c
#include <stdio.h>
int main() { /* <1> */
    printf("Hello, World!\n");
    return 0;
}
```

1. This is a comment for line 1.
```

[uwezi]

The standard Inline comment symbol in C is not //. It is only in ANSI C C99 and later.

Quarto uses /* ... */:

ok, I understand! Thank you very much for the explanation and example!

However "only in C99 and later" is kind of a statement in 2025. I have personally not or used any compiler which did support // as inline comment, I have been programming in C since 2004.