Re: Corrupted multibyte characters in command substitutions fixes may be worse than problem.

[Alex fxmbsw7 Ratchev]

On Tue, Feb 8, 2022 at 12:09 AM Ángel <angel@16bits.net> wrote:
>
> On 2022-02-07 at 11:55 +0100, Alex fxmbsw7 Ratchev wrote:
> > > > however my solution still stays
> > > > you just use memory locations instead of c strings
> > > > and those entries in memory are of course of known length, before
> > > > setting and all is fine
> > >
> > > "Your" solution is decades old.  Everyone knows how Pascal-style
> > > strings work.  This is not cutting-edge computer science.
> >
> > i dunno what pascal strings are, sorry
>
> Pascal strings refers to strings prefixed with their length:
> https://en.wikipedia.org/wiki/String_(computer_science)#Length-prefixed
>
> Basically, what you were proposing.

i see, thank you for good explaintion ( in your words not url )
>
>
> And as Veláquez said, it's ingenuous propose a solution nobody else
> asked for, expecting others to spend the effort of actually
> implementing it (plus the critics of their result, such as a limitation
> on the string length, or of wasted memory for every pointer).

well as im an outsuder i agree
else, i can just say, rather keep the nulls
you kept the \1'en and \xff :)) ( yeah not you, the c library language
or whatever )

greets