Hi Alex,
>> > http://picolisp.com/53823/59880452264949525~-2-1h.html based on
>> ...
>> And this is why putting session data in the URL is a terrible practice,
>> correct link: http://picolisp.com/5000/-2-1h.html
>
> I know your criticism of the URL strategy in PicoLisp, but I don't agree
> comple
Hi Doug,
> Basically replacing main() with:
> ...
> void miniPicoLisp_init( const char * home_dir )
> {
>heapAlloc();
>initSymbols();
>
>if (home_dir) {
> int l = strlen(home_dir) + 1;
> Home = malloc( l );
> memcpy(Home, home_dir, l );
> Home[ l ] = '\0';
>
Hi Tomas,
> I agree with José, I think the URL handling in PicoLisp is broken.
>
> > The main purpose of an URL is not to copy/paste it, and usually
> > mistakes like the above one can be easily avoided.
>
> Copy and pasting URL is one of the most important features.
Copying session-URLs is not
On Tue, Jun 21, 2011 at 10:28:53AM +0200, Alexander Burger wrote:
> > ago. This fallback might have to be application specific thing so maybe
> > the wiki software is broken from this point of view, not sure.
>
> Yes, I simply used the existing mechanisms, though a wiki is not a
> typical applica
On Tue, Jun 21, 2011 at 11:26:20AM +0200, Alexander Burger wrote:
>
> It would be cleaner if I removed that log in / log out mechanism. Then
> the "home" site would be only for viewing, browsing etc, and the "wiki"
> site allows to log in and modify things.
It would be better if the Wiki detected
Hi Jakob,
> It would be better if the Wiki detected a session URL and fell back to
> the original page.
exactly;-) Long time ago I described my set up to Henrik, see
http://logand.com/blog/picolisp-behind-nginx-proxy.html
As Alex uses home grown proxy called httpGate, it would need to be
probabl
--- On Tue, 6/21/11, Alexander Burger wrote:
> Yes, the Apply* lines are needed (or what does the "??"
> imply?).
I wasn't sure if I needed that for my initialisation - you answered my question
there.
> I see one remaining problem: The 'ErrRst' global, the error
> restart jump
> buffer, is not
Good bye Jerry Antosh :-(
You are now unsubscribed
Thank you so much and best wishes,
Jerry Antosh
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
I think I'm getting closer. The read() portion seems to work, in that the
correct characters are consumed.
I can then doPrint() on what doRead() returns - although I don't see the
customary parentheses around the list I hand that to doEval().
doEval() returns a value (an "any" pointer, whic
Tomas, I'm quite upset about your statement that "the URL handling in
PicoLisp is broken". This is not the case! It proved to be very
efficient and useful during more than a decade.
> http://logand.com/blog/picolisp-behind-nginx-proxy.html
This doesn't address José's original issue of encoding s
10 matches
Mail list logo