Re: SciTE 64-bit fails full lua integration

[Andre Dias]

On Thursday, August 2, 2012 2:48:23 PM UTC-3, Andre Dias wrote:

Migrating to squeeze, was not possible to obtain lua full integration.

Alternative solution (until better approach) at:

http://alsdias.blogspot.com.br/2012/08/migrating-32-bit-applications-to-debian.html

[Andre Dias]

[Neil Hodgson]

This isn't a 64-bit issue since the "dofile" example script works fine on 64-bit Mint 13.

SciTE currently builds in 64-bit mode with 0 warnings from G++ 4.6 and 4.7. The 64-bit bugs mentioned were fixed 8 years ago.

Neil

[Andre Dias]

On Thursday, August 2, 2012 4:21:55 PM UTC-3, gus...@gusnan.se wrote:

On Thursday, August 2, 2012 7:48:23 PM UTC+2, Andre Dias wrote:

Migrating to squeeze, was not possible to obtain lua full integration.

Alternative solution (until better approach) at:

http://alsdias.blogspot.com.br/2012/08/migrating-32-bit-applications-to-debian.html

This is reported in Debian as bug #585865 - see

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585865

for more details.

I've read the bug report.
I may be possibly wrong, but I do not agree about the way it's seen there.
SciTE may seam its own way between itself and lua.
Lua works pretty well on squeeze.
Compilation also runs well.
This kind of thing gets better approach if less coupled to external frameworks or conditions except those directly involved.
So,I've been thinking about a delegate layer to handle lua, responsible to get back its answer.
This would make SciTE's lua integration stronger and more stable, free from environment conditions.
The central idea would be to make lua as something like an internal module (library) under SciTE install dir.
A stand-alone approach.

Something I do agree about the comments on that bug report - SciTE without lua looses too much.

 

[Neil Hodgson]

Andre Dias:

> So,I've been thinking about a delegate layer to handle lua, responsible to get back its answer.
> This would make SciTE's lua integration stronger and more stable, free from environment conditions.
> The central idea would be to make lua as something like an internal module (library) under SciTE install dir.
> A stand-alone approach.

SciTE uses its own internal copy of Lua. I think someone wrote a patch that uses the system Lua and possibly Debian are using that but its not the default.

> Something I do agree about the comments on that bug report - SciTE without lua looses too much.

You can download SciTE and build it yourself:
http://prdownloads.sourceforge.net/scintilla/scite321.tgz?download
That way you get the most recent version with integrated Lua.

Neil