Re: [Pharo-users] CodeImporter. 256 literals limit

2017-08-31 Thread Andreas Sunardi
Esteban, I'm happy to report this package works for me, in my RH/CentOS 6 environment. I have to do a bit more since I have to install it in a network path (can't install in each server). If there's a download option instead of an rpm, such as that in Pharo 5 download website, that would be great.

Re: [Pharo-users] CodeImporter. 256 literals limit

2017-08-30 Thread Esteban Lorenzano
you can try the new (still experimental) packaging for Pharo: CentOS 6.8: # Add the repo $ yum-config-manager --add-repo http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/CentOS_6/devel:languages:pharo:latest.repo # Install 32bit packages (with X11 dependency for *-ui o

Re: [Pharo-users] CodeImporter. 256 literals limit

2017-08-29 Thread Andreas Sunardi
Point well taken. Unfortunately, I'm not in charge of the infrastructure. I don't know if my experience is typical or not, but it's difficult for IT to find a period to disrupt engineering projects, potentially breaking tools, without drawing fire from engineering :) On Tue, Aug 29, 2017 at 8:45

Re: [Pharo-users] CodeImporter. 256 literals limit

2017-08-29 Thread Richard Sargent
> > my work environment is using RedHat6/CentOS6 with glibc 2.12 > That's seven years of unpatched security vulnerabilities! Are you sure you really want to stay at such great risk? On Tue, Aug 29, 2017 at 8:30 AM, Andreas Sunardi wrote: > That sounds good. Unfortunately for me, my work enviro

Re: [Pharo-users] CodeImporter. 256 literals limit

2017-08-29 Thread Andreas Sunardi
That sounds good. Unfortunately for me, my work environment is using RedHat6/CentOS6 with glibc 2.12. Is there Pharo6 with glibc < 2.15 support. Or is there a way for me to build that myself? It's quite a departure to change my DSL into defining multiple methods. But that's my own problem. I'm ha

Re: [Pharo-users] CodeImporter. 256 literals limit

2017-08-29 Thread Clément Bera
Hi, If your tool works in Pharo 6, you can use the other bytecode set which supports up to 32k literals. To do so, go to: World Menu > Settings > Compiler > Encoder and pick SistaV1 instead of V3PlusClosures Try to load your code. The default Pharo 6 VM supports both bytecode sets. Alternatively

Re: [Pharo-users] CodeImporter. 256 literals limit

2017-08-29 Thread Marcus Denker
Hello, The new byte code set that we will use in the future does not hat this limitation. You can, but only in Pharo6 and later, the new byte code backend (it is called “SistaV1”). (this is a global preference to be enabled in the Settings). Marcus It is not yet used by default, but yo

[Pharo-users] CodeImporter. 256 literals limit

2017-08-28 Thread Andreas Sunardi
I have written a tool (Pharo5) where user gives an input file to it, where the content is a smalltalk code, a DSL. I used a subclass of CodeImporter class to evaluate this input file. Recently my user used an input file where it hit the 256 literal limit (total of unique string, number, method nam