[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
▼ Settings Mobile Home
4chan
/g/ - Technology


Thread archived.
You cannot reply anymore.




File: pepe-happy.gif (20 KB, 220x220)
20 KB GIF
strdup now in the libC
>>
how does this affect me
>>
>>110205783
use case?
>>
This is the worst news I've received in years.
>>
>>110205783
What is the advantage of this vs. malloc + strcpy
>>
>>110205913
it can be a syscall and 100% native
>>
>>110205913
Accounting for retards like you who think the equivalent involves strcpy.
>>
>>110205939
Something being in the C standard library does not mean it can be a syscall. These are completely unrelated concepts. A syscall is a function in the kernel which is invoked from user-space. The actual benefit is that it's portable now. Any platform that supports ISO C23 can now use strdup without depending on an external library.
>>
>>110207519
didnt ask nigga
>>
>>110207528
You didn't need to. I corrected you. Because your explanation to the question that was asked was wrong.
>>
>>110205783
It's still not asprintf.
>>
>>110205783
You should not use libc.
>>
>>110205783
what about strndup
>>110207612
>assprintf
>>
>>110206222
Retard.
>>
>str printer goes brrrrrr
BTC
bc1qtm4rep7kyp2p28hlkfktpnd0j7uew47vnt2mev
LTC
ltc1q9xlaysse0mpfwf025esd69kt9zu3md22gh23du
ETH
0x6abA18D203520c8F90ca63eE7426a7bC345D98e6
SOL
E5ekoiauCR8yiNp451dmuPzhUxo84P5x3m9WJBK5kxZe
XRP
r3jYXNdMk2Vz5hXhKCKE9re8uz93JQFG1r
DOGE
DSBq5jRWkiwmEh1G7zBwmQDgRkvRr61fmb
XMR
85CTwq5wGjWZw5GgzgwZPrHyZxpLXMK5oZSSSk5j4x9w1bpqzisaWAUZYaAPfh6rP2MZJcaFqF1XmEzkw6YCqJSS2Txu6Z8




Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.