fix: potential pointer invalidation with ft_buffer

This commit is contained in:
Khaïs COLIN 2025-03-09 14:39:55 +01:00
parent 836e24bcb7
commit 1c653d9665
Signed by: logistic-bot
SSH key fingerprint: SHA256:RlpiqKeXpcPFZZ4y9Ou4xi2M8OhRJovIwDlbCaMsuAo

View file

@ -6,7 +6,7 @@
/* By: khais <marvin@42.fr> +#+ +:+ +#+ */
/* +#+#+#+#+#+ +#+ */
/* Created: 2025/02/20 14:02:29 by khais #+# #+# */
/* Updated: 2025/03/06 16:51:58 by khais ### ########.fr */
/* Updated: 2025/03/09 14:39:50 by khais ### ########.fr */
/* */
/* ************************************************************************** */
@ -36,10 +36,10 @@ void push_char(t_token_build *builder, char c)
if (builder->cur_marker == NULL)
builder->cur_marker = ft_buffer_new();
if (builder->quote == '\0' || c == builder->quote)
ft_buffer_pushchar(builder->cur_marker, ' ');
builder->cur_marker = ft_buffer_pushchar(builder->cur_marker, ' ');
else
ft_buffer_pushchar(builder->cur_marker, builder->quote);
ft_buffer_pushchar(builder->cur_token, c);
builder->cur_marker = ft_buffer_pushchar(builder->cur_marker, builder->quote);
builder->cur_token = ft_buffer_pushchar(builder->cur_token, c);
}
void new_word(t_token_build *builder, char c)