Re: [DISCUSS] MessageBytes refactoring

2022-08-24 Thread Han Li
> 2022年8月24日 16:16,Mark Thomas 写道: > > On 24/08/2022 09:08, Rémy Maucherat wrote: >> On Tue, Aug 23, 2022 at 10:43 PM Mark Thomas wrote: >>> >>> Hi all, >>> >>> I've been looking at a fix for bug 66196. My ideas so far have revolved >>> around MessageBytes but the solutions are being made

Re: [DISCUSS] MessageBytes refactoring

2022-08-24 Thread Mark Thomas
On 24/08/2022 09:08, Rémy Maucherat wrote: On Tue, Aug 23, 2022 at 10:43 PM Mark Thomas wrote: Hi all, I've been looking at a fix for bug 66196. My ideas so far have revolved around MessageBytes but the solutions are being made more complex by the current behaviour of MessageBytes in some

Re: [DISCUSS] MessageBytes refactoring

2022-08-24 Thread Rémy Maucherat
On Tue, Aug 23, 2022 at 10:43 PM Mark Thomas wrote: > > Hi all, > > I've been looking at a fix for bug 66196. My ideas so far have revolved > around MessageBytes but the solutions are being made more complex by the > current behaviour of MessageBytes in some cases. > > For example (I'm using

[DISCUSS] MessageBytes refactoring

2022-08-23 Thread Mark Thomas
Hi all, I've been looking at a fix for bug 66196. My ideas so far have revolved around MessageBytes but the solutions are being made more complex by the current behaviour of MessageBytes in some cases. For example (I'm using strings in place of byte[] and char[] to keep it simple):