Alexander Burger writes:
Hi Alex,
>> is it "normal" that a simple 'kill' won't kill PicoLisp processes, only
>> with option 'KILL it works?
>
> No.
>
> A "normal" kill with SIGTERM (i.e. -15) should work.
>
> SIGKILL (i.e. -9) should be used only in extreme emergencies, because it
> may cause th
> On Wed, 17 Jul 2013 09:22:14 +0200
> Thorsten Jolitz wrote:
>
> ..[snip]..
> I ran into this problem when experimenting with the
> web-framework and my app got into a bad state. When restarting then,
> PicoLisp tells me something like 'Port is already used', so I tried
> to kill the still runni
Rowan Thorpe writes:
>> On Wed, 17 Jul 2013 09:22:14 +0200
>> Thorsten Jolitz wrote:
>>
>> ..[snip]..
>> I ran into this problem when experimenting with the
>> web-framework and my app got into a bad state. When restarting then,
>> PicoLisp tells me something like 'Port is already used', so I t
When developing web apps I keep the code for the server and the rest
separate and reload the rest on every request. No need for restarts at all
that way.
Unless you're actually fiddling with the actual server code, then it can't
be helped I suppose...
On Wed, Jul 17, 2013 at 3:33 PM, Thorsten Jo
Henrik Sarvell
writes:
Hi Henrik,
> When developing web apps I keep the code for the server and the rest
> separate and reload the rest on every request. No need for restarts at
> all that way.
interesting idea, not sure how you actually do that, but would make
things smoother in the not so rar
> On Wed, 17 Jul 2013 16:14:11 +0700
> Henrik Sarvell wrote:
>
> When developing web apps I keep the code for the server and the rest
> separate and reload the rest on every request. No need for restarts
> at all that way.
>
> Unless you're actually fiddling with the actual server code, then it
On Wed, Jul 17, 2013 at 01:28:59PM +0300, Rowan Thorpe wrote:
> ..for such times (and for those times that you generally can't be so
> organised), there is the "sledgehammer approach" - SO_REUSEADDR
Why "sledgehammer approach"? This is quite normal, as I see it.
The PicoLisp network functions alw
> On Wed, 17 Jul 2013 12:56:35 +0200
> Alexander Burger wrote:
>
> > On Wed, Jul 17, 2013 at 01:28:59PM +0300, Rowan Thorpe wrote:
> > ..for such times (and for those times that you generally can't be so
> > organised), there is the "sledgehammer approach" - SO_REUSEADDR
>
> Why "sledgehammer ap
"interesting idea ... "
Through the http server you can call any PL function, in that function you
(load) stuff before doing what you need to do.
>From the above it kind of follows that I use a single
bootstrap/entry/routing function, so I only need to do the loads there and
nowhere else.
On
Hi Alex,
Today I got the idea that I would like to run Ersatz in Eclipse. To
obtain the PicoLisp.java source for the ersatz/picolisp.jar, I did
cd ersatz/
pil mkJar +
I then created an empty Java project in Eclipse and imported the
PicoLisp.java source. To avoid a NullPointerException when ru
Hi Jon,
thanks for the input!
> obtain the PicoLisp.java source for the ersatz/picolisp.jar, I did
> cd ersatz/
> pil mkJar +
>
> I then created an empty Java project in Eclipse and imported the
> PicoLisp.java source. To avoid a NullPointerException when running my
> project, I entered "-DPID
Hi Alex,
> Hi Jon,
>
> thanks for the input!
>
>> obtain the PicoLisp.java source for the ersatz/picolisp.jar, I did
>> cd ersatz/
>> pil mkJar +
>>
>> I then created an empty Java project in Eclipse and imported the
>> PicoLisp.java source. To avoid a NullPointerException when running my
>> proje
Hi Jon,
> > because 'next' is in fact used (and needed!) in all those cases.
> >
> > How come?
>
> I cannot see one place where the value of 'next' is used (read/retrieved).
> Can you tell me which line?
Yes, for example the one where Eclipse is complaining about:
The value of the local vari
Hi Alex,
> Hi Jon,
>
>> > because 'next' is in fact used (and needed!) in all those cases.
>> >
>> > How come?
>>
>> I cannot see one place where the value of 'next' is used
>> (read/retrieved).
>> Can you tell me which line?
>
> Yes, for example the one where Eclipse is complaining about:
>
>
Hi Jon,
> > next = Env.Next; Env.Next = 0;
> >
> > So here 'next' is used.
>
> Not really. A value (from Env.Next) is stored in 'next', but that value is
> never retrieved from 'next' later. Therefor 'next' is considered useless.
Ah! Cool! That's the problem.
'next' is indeed necessar
On Wed, Jul 17, 2013 at 08:24:45PM +0200, Alexander Burger wrote:
> I'll fix that. Thanks!
Done :)
I've fixed all other places too where it complained about unused
variables (these were really unused ones), and have uploaded a new
release.
Please test again whenever you have time!
♪♫ Alex
--
U
16 matches
Mail list logo
