- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Does OSSubprocess works on ARM vm?

by Denis Kudriashov

2017-05-16 13:01 GMT+02:00 K K Subbu <kksubbu.ml(a)gmail.com>: > > If you run it from command line, does it list the files on the tty? Then > it could be a bug in redirectStdout method. > Yes, it works from command line

May 16, 2017

Re: [Pharo-dev] Does OSSubprocess works on ARM vm?

by K K Subbu

On Tuesday 16 May 2017 04:26 PM, Denis Kudriashov wrote: > > I checked again. It not works on Raspberry same way: empty string > returns. Not know how it would be on other Linux If you run it from command line, does it list the files on the tty? Then it could be a bug in redirectStdout method. HTH .. Subbu

May 16, 2017

Re: [Pharo-dev] Does OSSubprocess works on ARM vm?

by Denis Kudriashov

2017-05-15 22:19 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > 2017-05-15 18:10 GMT+02:00 Alistair Grant <akgrant0710(a)gmail.com>: > >> And if I execute the following in a playground: >> >> | ls | >> OSSUnixSubprocess new >> shellCommand: 'ls ~'; >> redirectStdout; >> runAndWaitOnExitDo: [ :process :outString | >> ls := outString >> ]. >> ls. >> >> >> It returns the expected value. >> > > Yes, it works for me too on Mac. Maybe I did something wrong on Raspberry. > I will check tomorrow. I checked again. It not works on Raspberry same way: empty string returns. Not know how it would be on other Linux

May 16, 2017

Re: [Pharo-dev] Does OSSubprocess works on ARM vm?

by Denis Kudriashov

2017-05-15 18:10 GMT+02:00 Alistair Grant <akgrant0710(a)gmail.com>: > And if I execute the following in a playground: > > | ls | > OSSUnixSubprocess new > shellCommand: 'ls ~'; > redirectStdout; > runAndWaitOnExitDo: [ :process :outString | > ls := outString > ]. > ls. > > > It returns the expected value. > Yes, it works for me too on Mac. Maybe I did something wrong on Raspberry. I will check tomorrow. Thank's for help

May 15, 2017

Embeddable/scalable Smalltalk VM needs funding for release (repost/update from squeak-dev)

by Zak Fenton

Hi folks. I posted earlier in squeak-dev about a Smalltalk implementation I've been working on. The first post was a bit unwieldy, but there was at least some interest so I'm posting an update to vm-dev and pharo-dev. Main strong points are that it's embeddable (like Lua or SQLite) and scalable (like Erlang). There are weak points too, of course (e.g. hot loop performance will be much worse than Squeak/Pharo at this point). The VM itself is pure C and has no dependencies apart from libc and libm. It doesn't require a filesystem (you can pipe VM images through custom stream implementations or arrays) and it should run well in tight (~1MB) memory situations. The extension system is similar to the Unix system call and virtual filesystem APIs, so it's kind-of object oriented but in a very "C" way. All extension resources are managed properly (so the system can clean up safely and/or warn you if you allocate memory and don't deallocate it, for example). Extensions are available for cells (threads/individual VMs), shared memory (so different cells can communicate efficiently - but also with memory protection and calling features for implementing domain-specific JIT compilers), windowing and event handling (based on SDL2) and 2D graphics rendering (based on Cairo). There are some higher-level libraries (stylable GUI system, tight OS integration, 3D modelling, etc.). It's polished in some ways (there's a test suite, an integrated help system, colour shell, etc.), but it needs a lot more refinement in others (the current GUI style is terrible, it needs more documentation, there's only minimal support for keyboard entry, no networking library, etc.). I'd like to release it (ideally as 100% public domain/CC0), but I don't want to do so without some way of funding development. The project promises a lot and I want to actually deliver with some ongoing updates and support (and being able to pay rent next week would also be a plus), so I'm not interested in just dumping it on GitHub and calling it a day. So I'm open to any suggestions as to how to fund this project at least in the short term and how it might fit into the wider Squeak/Pharo/Smalltalk ecosystems, as well as any technical criticism relating to the implementation itself. I've put together a basic website describing the implementation in a bit more detail (sorry, no downloads yet): http://a4vm.info/ -Zak.

May 15, 2017

Re: [Pharo-dev] Does OSSubprocess works on ARM vm?

by Alistair Grant

On Mon, May 15, 2017 at 04:10:17PM +0000, Alistair Grant wrote: > On Mon, May 15, 2017 at 08:14:44AM -0700, Eliot Miranda wrote: > > > > > > On Mon, May 15, 2017 at 8:09 AM, Damien Pollet <damien.pollet(a)gmail.com> wrote: > > > > My point was, if #shellCommand: accepts a single string for a whole > > command, then surely it passes it to a system shell already, so why nest a > > bash in between? (effectively running the equivalent of sh -c "bash -c \"ls > > ~\"') > > > > > > Clearly it doesn't do that otherwise Denis wouldn't have found that tile was > > unexpanded. I agree with you that it should. shellCommand: feels like a > > misnomer otherwise. > > I'm not sure why Denis is having problems, but... > > OSSUnixSubprocess>>shellCommand: aShellCommandString > "This is a simple facility method for the cases when the user wants to use shell as the program. > This way, the user can directly send > shellCommand: 'ls -la | grep Pharo > /tmp/test.txt ' with the whole string > rather than having to do set the command sh, send the '-c' argument, etc etc etc. > We first try to use the SHELL defined in the OS by getting the env variable $SHELL. > If not found, then we fallback to /bin/sh" > command := Smalltalk platform environment at: 'SHELL' ifAbsent: ['/bin/sh']. > arguments := Array with: '-c' with: aShellCommandString. > > > And if I execute the following in a playground: > > | ls | > OSSUnixSubprocess new > shellCommand: 'ls ~'; > redirectStdout; > runAndWaitOnExitDo: [ :process :outString | > ls := outString > ]. > ls. > > > It returns the expected value. One thought: Denis, are you using a non-English keyboard? Is there any chance that what you are entering looks like a tilda, but is some other unicode character? Maybe copy-and-paste the code I entered above? Cheers, Alistair > > On 15 May 2017 at 16:28, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > Hi Damien, > > > > On May 15, 2017, at 6:44 AM, Damien Pollet <damien.pollet(a)gmail.com> > > wrote: > > > > > > On 15 May 2017 at 15:26, Eliot Miranda <eliot.miranda(a)gmail.com> > > wrote: > > > > Try something like > > > > shellCommand: 'bash -c ''ls ~'''; > > > > > > But then that would run ls inside of bash inside of the system > > shell (/bin/sh), wouldn't it? What's the point? > > > > > > -c's argument is parsed by the shell so one gets full expansion. > > Further, if there are arguments after the string, they are assigned to > > the positional parameters, so that > > > > sh -c 'echo ~/$0' foo > > > > prints /Users/eliot/foo > > > > That may be useful.

May 15, 2017

Re: [Pharo-dev] Does OSSubprocess works on ARM vm?

by Alistair Grant

On Mon, May 15, 2017 at 08:14:44AM -0700, Eliot Miranda wrote: > > > On Mon, May 15, 2017 at 8:09 AM, Damien Pollet <damien.pollet(a)gmail.com> wrote: > > My point was, if #shellCommand: accepts a single string for a whole > command, then surely it passes it to a system shell already, so why nest a > bash in between? (effectively running the equivalent of sh -c "bash -c \"ls > ~\"') > > > Clearly it doesn't do that otherwise Denis wouldn't have found that tile was > unexpanded. I agree with you that it should. shellCommand: feels like a > misnomer otherwise. I'm not sure why Denis is having problems, but... OSSUnixSubprocess>>shellCommand: aShellCommandString "This is a simple facility method for the cases when the user wants to use shell as the program. This way, the user can directly send shellCommand: 'ls -la | grep Pharo > /tmp/test.txt ' with the whole string rather than having to do set the command sh, send the '-c' argument, etc etc etc. We first try to use the SHELL defined in the OS by getting the env variable $SHELL. If not found, then we fallback to /bin/sh" command := Smalltalk platform environment at: 'SHELL' ifAbsent: ['/bin/sh']. arguments := Array with: '-c' with: aShellCommandString. And if I execute the following in a playground: | ls | OSSUnixSubprocess new shellCommand: 'ls ~'; redirectStdout; runAndWaitOnExitDo: [ :process :outString | ls := outString ]. ls. It returns the expected value. Cheers, Alistair > On 15 May 2017 at 16:28, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi Damien, > > On May 15, 2017, at 6:44 AM, Damien Pollet <damien.pollet(a)gmail.com> > wrote: > > > On 15 May 2017 at 15:26, Eliot Miranda <eliot.miranda(a)gmail.com> > wrote: > > Try something like > > shellCommand: 'bash -c ''ls ~'''; > > > But then that would run ls inside of bash inside of the system > shell (/bin/sh), wouldn't it? What's the point? > > > -c's argument is parsed by the shell so one gets full expansion. > Further, if there are arguments after the string, they are assigned to > the positional parameters, so that > > sh -c 'echo ~/$0' foo > > prints /Users/eliot/foo > > That may be useful.

May 15, 2017

Re: [Pharo-dev] Does OSSubprocess works on ARM vm?

by Sven Van Caekenberghe

> On 15 May 2017, at 18:03, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > > 2017-05-15 16:55 GMT+02:00 K K Subbu <kksubbu.ml(a)gmail.com>: > What exactly are you trying to do? If you want the list of entries in ~ directory, you could use FileDirectory methods: > > (FileDirectory on: (OSProcess thisOSProcess environmentAt: 'HOME')) entries collect: [ :f | f name ]. > > My question was only about tilda usage. > (FileDirectory is not exists in Pharo anymore. We moved to FileSystem project) FileLocator home children

May 15, 2017

Re: [Pharo-dev] Does OSSubprocess works on ARM vm?

by Denis Kudriashov

2017-05-15 16:55 GMT+02:00 K K Subbu <kksubbu.ml(a)gmail.com>: > What exactly are you trying to do? If you want the list of entries in ~ > directory, you could use FileDirectory methods: > > (FileDirectory on: (OSProcess thisOSProcess environmentAt: 'HOME')) > entries collect: [ :f | f name ]. > My question was only about tilda usage. (FileDirectory is not exists in Pharo anymore. We moved to FileSystem project)

May 15, 2017

Re: [Pharo-dev] PharoLauncher prepared for Pharo 7

by Stephane Ducasse

Thanks! We should produce a new version of the launcher and push it more but too busy. stef On Mon, May 15, 2017 at 9:15 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > Pharo Launcher was updated for Pharo 7 already: > > ----------------------------------------------------------- > Name: PharoLauncher-Core-TorstenBergmann.105 > Author: TorstenBergmann > Time: 15 May 2017, 9:12:21.430226 am > UUID: 9b8faeb3-da25-49e9-bdf4-0c2b130ed357 > Ancestors: PharoLauncher-Core-CyrilFerlicot.104 > > Adopt to Pharo 70 already > > > after loading ensure to run > > PhLTemplateGroupRepository resetGroups. > > > > the new directory http://files.pharo.org/image/70/ is still empty > until the middle of the week. > > Have fun > T. > >

May 15, 2017