On Wed, 17 Oct 2001, Gregor N. Purdy wrote:
> Its still likely that I'm misunderstanding the intent, but I think
> that a .pbc file created by me with LANG=C is not necessarily going
> to generate string constants that have the same meaning when you go
> to run it on your platform of choice, which
At 01:49 PM 10/17/2001 +0100, Simon Cozens wrote:
>On Wed, Oct 17, 2001 at 08:21:51AM -0400, Gregor N. Purdy wrote:
> > I may be misunderstanding, but I think 'strnative' needs to go away
> > and we need to determine the precise native encoding,
>
>Please don't apply this; I think you are misunder
At 12:37 PM 10/17/2001 -0400, James Mastros wrote:
>On Wed, 17 Oct 2001, Gregor N. Purdy wrote:
> > 2. The encoding for the chunk-o-memory the interpreter is about
> > to turn into a STRING, having found said chunk in the packfile's
> > const_table.
>Perhaps we should always output str
On Wed, 17 Oct 2001, Gregor N. Purdy wrote:
> 2. The encoding for the chunk-o-memory the interpreter is about
> to turn into a STRING, having found said chunk in the packfile's
> const_table.
Perhaps we should always output string constants as UTF8? This would
avoid the problems with
Simon --
> > I may be misunderstanding, but I think 'strnative' needs to go away
> > and we need to determine the precise native encoding,
>
> Please don't apply this; I think you are misunderstanding.
> strnative is equivalent to LANG=C. It *is* the precise native
> encoding.
No problem. I was
On Wed, Oct 17, 2001 at 08:21:51AM -0400, Gregor N. Purdy wrote:
> I may be misunderstanding, but I think 'strnative' needs to go away
> and we need to determine the precise native encoding,
Please don't apply this; I think you are misunderstanding.
strnative is equivalent to LANG=C. It *is* the
