unsubscribe

Re: What parts of picolisp did you have the most trouble understanding?

Hi Alex, Op di 31 jul. 2018 om 17:34 schreef Alexander Burger : > > But 'cut' is *not* a destructive function. It does not modify the list in > any > way. Only the variable which points to the list is modified. > OK. That isn't totally obvious, but of course you are right as shown per this

Re: Survey results

Hi all, because I was busy I'm a bit late to react :) Thanks for the heads up, the concise results and also the very useful answers to open questions! To avoid further noise, I'll contact those that (I think) volunteered to (try to) help with the Wiki in private. Apart from me I have 4

Re: Testing test.l

Indeed a shortcoming of WSL. WSL works kind of OK after the april 2018 update. But calls to specific native Linux system routines often yield strange results. Also the output of standard Linux commands in WSL is often plain useless or very limited. Maybe this will improve in the near future :)

Re: Reminder on Wiki survey

Thanks! Op za 30 jun. 2018 om 13:59 schreef Timur Ismagilov : > I voted. Just letting you know. > > — bouncepaw > > > Исходное сообщение -------- > От: Arie van Wingerden > Дата: 30.06.2018 16:20 (GMT+05:00) > Кому: picolisp@software-lab.de > Тема:

Reminder on Wiki survey

Hi, we got 9 responses so far, but we guess there are a lot more participants / lurkers in this mailing list. Please fill out the survey here if you haven't done that yet: https://esurv.org/?s=MOIEMH_753ad7ff Thanks to those who already did participate :) Best, Arie

Re: Wiki progress update ...

Hi Nehal, Op ma 25 jun. 2018 om 13:29 schreef Nehal : > While observing new changes made in picolisp wiki css, I observed on > https://picolisp.com/wiki/?PCE: > > 1. *Numbering* error of headings. 3 comes after 4 again! > ​Corrected.​ 2. "On Rosettacode you can find a wealth of examples on a

Re: Wiki progress update ...

Thx. Manuel! Op ma 25 jun. 2018 om 14:09 schreef Manuel Cano : > Hi, > > I've corrected the missing quote: ...known "Perl Cookbook. > > :) > > > Kind regards, > Manu > > 2018-06-01 17:19 GMT+02:00 Arie van Wingerden : > >> The first section of PLEAC

Re: Wiki css

Hi Jean-Christophe, Op ma 25 jun. 2018 om 12:04 schreef Jean-Christophe Helary < brandel...@gmail.com>: I agree. But it is always difficult to discuss a proposal before seeing > some kind of implementation. > ​Right. Thtat's a thing I really need to change.! > I think it is possible to

Re: Wiki css

No problem :) Op ma 25 jun. 2018 om 12:04 schreef Manuel Cano : > Hi Arie, > > Sorry. I've mistyped you name! > > > Kind regards, > Manu > > 2018-06-25 11:41 GMT+02:00 Arie van Wingerden : > > > Hi Manuel, > > > > I like as it is now. Ari has made

Re: Wiki css

Hi Johann, I would also keep it > ​ ... > ​OK. You don't like the updates I guess.​ > ​ > and somebody finds something annoying (like italic > headlines) they should just send an "upgraded" css to the mailing list and > have some people try it out. > It indeed would be nice *if* people did

Re: Wiki css

Hi Manuel, I like as it is now. Ari has made a good job, don't throw it away. ​Pffft. I really thought it was all bad news. Thx. If it was hard for someone before, they could have done what Ari has made. ​That's right. But it is *really* difficult to do things that everybody likes ...​ ​Thx!

Re: Wiki css

Hi Alex, might be a good Idea. But the mailing list and IRC don't seem to be really appropriate to do voting. ​ Does somebody know if there is a good free online possibility out there to do voting on several things in one go? If so, I am surely willing to take the effort and follow up

Wiki css

Hi all, after reading a few reactions and also my struggle to get things right (in *my* opinion), I realize that it really is impossible to please everybody. Given the fact that also I seem to be the only person not liking the old CSS and that the new CSS is a "regression" it is much better to

Re: Wiki - asking for last calls on fonts etc.

Hi Nehal, I see.Well, my biggest wish is to add more useful content than changing the layout. For me personally, the layout wasn't so nice. Guessing that this would be the case for other people, I started to try to help. Maybe we should wait for a while for all reactions. Ultimate choice could

Re: Wiki - asking for last calls on fonts etc.

Hi Alexander, I haven't been following the recent website changes, but right now it > seems the picolisp.com website is much worse than it used to be. A > regression. > ​Well, that is a blow to take in ... > - text is too small. Please use browser relative sizes in "em" and "%" > instead of

Re: Wiki updated fonts etc.

gt; > On Jun 24, 2018, at 18:32, Arie van Wingerden wrote: > > Hi Jean-Christophe, > > thanks for the feedback! > > Would you be so kind to update these things yourself? > > It is quite impossible to forsee every wish. I just tried :) > > If you remove bold

New page in Wiki

Hi, under "Start here" on this page https://picolisp.com/wiki/?documentation I added a page called "The pros and cons of PicoLisp". This is a more concise version of the current Tractatus Pico-Blaesicus, which currently is still used as a demo for saerving web pages and paragraph folding. I

Re: Wiki updated fonts etc.

on macOS} > It is not possible to install picolisp on macOS, or even to build it > without significant modifications to the code. The easiest way to access it > on your machine is to install it on a lightweight Linux system and to ssh > to it. > > JC > > On Jun 24, 2018, at 1:

Re: Screenshot of local Wiki

18 om 14:17 schreef Joh-Tob Schäg : > >> Hello, >> >> i find the black on black text very hard to read >> >> 2018-06-23 12:16 GMT+02:00 Arie van Wingerden : >> >>> >>> >>

Wiki updated fonts etc.

Hi all, today the CSS for the Wiki has been updated. It is really difficult to find appropriate fonts, font-sizes and -colors. 1. menu now has bright white letters, which is better for people having difficulty with reading 2. headers are a bit smaller, but maybe they need a bit of adjustment

Re: Screenshot of local Wiki

What do you mean? Where precisely? Op za 23 jun. 2018 om 14:17 schreef Joh-Tob Schäg : > Hello, > > i find the black on black text very hard to read > > 2018-06-23 12:16 GMT+02:00 Arie van Wingerden : > >> >> >

Screenshot of local Wiki

Re: Proposal for Wiki CSS changes

Yes, that's ok. I'll setup the Wiki locally and try to get it as proposed :) Thx! 2018-06-22 18:51 GMT+02:00 Alexander Burger : > Hi Arie, > > > well, I will try :) > > But my knowledge of this kind of stuff is very limited ... > > > > This will take a bit of time. > > No hurry :) > > I'd

Re: Proposal for Wiki CSS changes

Hi Alex, well, I will try :) But my knowledge of this kind of stuff is very limited ... This will take a bit of time. Best, Arie 2018-06-22 18:05 GMT+02:00 Alexander Burger : > Hi Arie, > > > please find attached the desired changes to the CSS. > > It is not clear to me what has to be

Proposal for Wiki CSS changes

Hi all, please find attached the desired changes to the CSS. Apart from a few obvious changes, there are a few things Alex has to take into account: - I assumed that lines entered without specific mark-up would be put in paragraphs - the background color of the menu - a few tips of

Re: Wiki - asking for last calls on fonts etc.

; Text is zoomable and responsive in landscape/portrait mode. > > I like it (except the lightgreen background color :-), but that's out of > scope of headers and top text). > > Greetings, Olaf > > > > On 18.06.2018 11:16, Arie van Wingerden wrote: > >> Hi all, >> &g

Re: Wiki - asking for last calls on fonts etc.

Hi Karl-Heinz, yes. I understand that :) After friday I'll post my proposed changes here. With those it will be possible to use the CSS defaults by the easy Wiki mark-up. Thx. for helping! Arie 2018-06-19 23:12 GMT+02:00 Karl-Heinz Kreis : > Hi Arie, > > When the markup for headings is

Re: Wiki - asking for last calls on fonts etc.

Hi Karl-Heinz, ok. That is out of my reach :) @Alex can we take that into account when updating the rest of the CSS? Thx! Arie 2018-06-18 14:16 GMT+02:00 Karl-Heinz Kreis : > Hi all, > > On the Menu on top, try a lighter textcolor, ie. lightgrey, to enhance > contrast. Stark white could be

Re: Wiki - asking for last calls on fonts etc.

: > Arie, > > Is there a reason why there are 2 different fonts: one for the > Introduction and one for the rest ? > > JC > > > On Jun 18, 2018, at 18:16, Arie van Wingerden wrote: > > Hi all, > > since I really want to push forward with the Wiki, I'd

Wiki - asking for last calls on fonts etc.

Hi all, since I really want to push forward with the Wiki, I'd like to ask everybody to have a look at this page: https://picolisp.com/wiki/?Documentation Question: - are the headers OK? - is the top text OK (under header "Introduction"? Note that we wish to recognize visually impaired people!

Re: Wiki fonts etc.

I changed that now. Is that OK? 2018-06-18 10:53 GMT+02:00 Jean-Christophe Helary : > > > On Jun 18, 2018, at 17:05, Arie van Wingerden wrote: > > Hi Michel, > > good to know! > > Please let me know if: > - the sub headers are OK > - the upper text i

Re: Wiki fonts etc.

:50 GMT+02:00 Michel Pelletier : > I am also slightly vision impaired and prefer higher contrast and/or > larger fonts. > > Quite a few good tips here https://webaim.org/techniques/fonts/ > > On Sun, Jun 17, 2018 at 6:25 AM, Arie van Wingerden > wrote: > >> Hi all,

Re: Wiki fonts etc.

all-back > values too. > Also, the code examples have a very tight font that I find hard to read on > the screen, redefining that as at least a standard monospace would be nice > :) > > Jean-Christophe > > > On Jun 17, 2018, at 22:25, Arie van Wingerden wrote: > > Hi all, &

Wiki fonts etc.

Hi all, being busy with the Wiki, I try to find some nice standards for fonts. On this page https://picolisp.com/wiki/?documentation all elements are used. I'd like to use: - main header: using current markup 4{ } - all sub headers: color: MidnightBlue;

Reworked main documentation page

Hi all, I reworked the main doc page a bit: - bit more stylish (smaller font headers) - consistent grouping - moved a few links to the now separate examples page - and v.v. Also I intend to continue to rework pages. My todo's for near future are: - rework the frontpage of the

Re: PLEAC last part finished (File Access)

OK. I changed that to an example using redirection of STDIN to a file. 2018-06-16 15:56 GMT+02:00 Arie van Wingerden : > Or do you mean e.g. something line: > ./script ?? > > Thx. > > 2018-06-16 15:38 GMT+02:00 Arie van Wingerden : > >> Hi Alex, >> >&g

Re: PLEAC last part finished (File Access)

Or do you mean e.g. something line: ./script : > Hi Alex, > > please have a look. > > I am still not very sure about the read STDIN until EOF. > > I created a small script, but when is EOF of STDIN really signalled??? > > Maybe a small example? > > Thx, >Arie >

PLEAC last part finished (File Access)

Hi Alex, please have a look. I am still not very sure about the read STDIN until EOF. I created a small script, but when is EOF of STDIN really signalled??? Maybe a small example? Thx, Arie

Re: PLEAC Pattern Matching ready

​Hi, ​ > Yes, fully. But also (>= "Z" C "A") > ​Right! ​ > > > Also a few lines down: (chop "abcd efg"))) > > ​?? What is wrong? > Only the spacing of closing parens (chop "abcd efg") ) ) > ​OK! I'll take the pp advice :) Thx. again! Arie​

Re: PLEAC Pattern Matching ready

Hi, This is a little inefficient, and the indentation and parenthesis > placements are a > not right. I would suggest: > >(de isalpha? (Lst) > (fully > '((C) > (or (>= "Z" C "A") (>= "z" C "a")) ) > Lst ) ) > ​Great! Nice function. Didn't know that :)​ >

Question on PLEAC example

Hi Alex, just started on chapter 7. You give this code as an example. # Read STDIN till EOF : (setq Var (in NIL (till NIL T))) This is a line a peaceful line it is not drunk it drinks no wine # Here I pressed ctrl+d which forces PicoLisp to end As discussed earlier you

Lubuntu

Hi, instead of Windows WSL. I now have Lubuntu running virtually. TL;DR; After a period of working with Windows WSL I was fairly satisfied. However, things are very different under the hood, so that some PicoLisp stuff just doesn't work. I imagine that the Micro$oft people are not able to

PLEAC Pattern Matching ready

Hi Alex, please check chapter 6 on pattern matching. This chapter and the following one are incomplete and all the rest was not yet done. Maybe that is something for the future:) I hope that some other PicoLispers have the courage to dive in and make PLEAC more complete. I'll then take care of

Re: Tractatus Blaesicus

OK. Then I'll proceed that way :) Op wo 13 jun. 2018 19:48 schreef Alexander Burger : > Hi Arie, > > > My idea was indeed to replace the current contents with something else. > > Tractatus logico-philosophicus is a great suggestion (mind you, I > didn'read > > it yet ... :) > > Haha, me

Re: Tractatus Blaesicus

​​Hi Alex, > Yes, but the point is not the text, but the interaction with it. Understood. That's why a demo of such kind is still needed :) > In fact, it was created as a parody of Wittgenstein, not as a serious tool to > explain or teach PicoLisp. A nice exercise would be to replace the

Re: Tractatus Blaesicus

be better appreciated I think ... Agreed? /Arie 2018-06-13 13:34 GMT+02:00 Alexander Burger : > On Wed, Jun 13, 2018 at 12:05:38PM +0200, Arie van Wingerden wrote: > > Of course it *is* useful, however, reading it is very tedious, not the > > least because every time you wis

Re: Tractatus Blaesicus

; I think this would be a much better opener instead that cheeky first > paragraph. > > -beneroth > > > Am 2018-06-13 12:05, schrieb Arie van Wingerden: > >> Hi Alex, >> >> would it be an ides to transfer the contents of this to a simpler page >> on the

Tractatus Blaesicus

Hi Alex, would it be an ides to transfer the contents of this to a simpler page on the Wiki? Of course it *is* useful, however, reading it is very tedious, not the least because every time you wish to open a sub paragraph, the page "jumps" to the top. Personally I think this could be done

Re: Wiki progress again: hashes

Added that example. You'd like it :) 2018-06-13 9:22 GMT+02:00 Arie van Wingerden : > Hi Alex, > > please be aware that all those examples were (long ago) created by > yourself :) > So all creadits go to you! > > I only transfer them to the Wiki, with a nice layout

Re: Wiki progress again: hashes

though ... I'll look into 'rassoc' and add that as an example. In the future I hope to create more examples myself. Best, Arie 2018-06-12 20:27 GMT+02:00 Alexander Burger : > On Tue, Jun 12, 2018 at 04:39:34PM +0200, Arie van Wingerden wrote: > > the 'hashes' section is now ready.

Re: Question on PLEAC hashes example

Hi Alex, done! Thx, Arie 2018-06-12 16:05 GMT+02:00 Alexander Burger : > Hi Arie, > > > This example (in "Traversing a Hash"): > > > >#- > ># download the following standalone program > >#!/usr/bin/picolisp /usr/lib/picolisp/lib.l > > > >(load

Re: Wiki progress ...

Hi Alex, > Is this intended? Or is the third line missing? ;) > ​Indeed; corrected :)​ In "4.3.1. Iterate over a list" you could put in addition to the 'for' loop: > >(mapc println mylist) # Probably better Mylist > ​Done and done.​ > Note that instead of > >: (for I (length lst) >

Wiki progress again: hashes

Hi Alex, the 'hashes' section is now ready. Please have a look :) Best, Arie

Failing example PLEAC

Hi Alex, the attached program dutree.l seems to misbehave in Windows WSL. Would you please verify that it works correctly under native Linux? TIA, Arie dutree.l Description: Binary data

Wiki progress ...

Hi all, the page on "Arrays" is ready. This was quite abit of work :) In this case I had to dive in a few times and with some great help I learned a lot from that. My mindset had to change quite a bit. I worked with other Lisps, which (almost) all were lexically scoped. Now I saw quite a few

Re: picolisp at last ?

OK. Good to hear you succeeded :) 2018-06-12 9:36 GMT+02:00 Jean-Christophe Helary : > > > On Jun 12, 2018, at 15:28, Arie van Wingerden wrote: > > OK. > My WSL installation is Ubuntu based. > Could you try e.g. Lubuntu in a VM? > > > Actually I got it working

Re: picolisp at last ?

OK. My WSL installation is Ubuntu based. Could you try e.g. Lubuntu in a VM? I got a recent version of PicoLisp just installing it using apt, and it works well ... Op ma 11 jun. 2018 23:31 schreef Jean-Christophe Helary < brandel...@gmail.com>: > > > On Jun 12, 2018, at 2:36, Ari

Re: Wiki progress

time for picolisping in the future :-) > > > Apologize for the trouble, > > Olaf > > > > On 11.06.2018 12:49, Arie van Wingerden wrote: > > Hi Olaf, > > > > as far as I understood Alex the main CSS file currently used is > > maintained centrally. > > &g

Re: picolisp at last ?

Hi Jean-Christophe, what host system are you using? If on Windows 10 with the last april update WSL is really stable! And PicoLisp works just fine. There are a few "limits" in that some features do not exist in WSL, e.g. there is no /etc/passwd file and such. For the rest all works OK. Best,

Re: Wiki progress

s (*)${text-align: center; > class: hilited-background; > } 2{PicoLisp Documentation}} > > and defined in css file: > hilited-background { background-color: black; color: white; } > > > > > > On 09.06.2018 17:40,

Re: Stuck at PLEAC example

So I guess that the possibility of using This as a formal parameter is a goodie associated with dynamic scoping, which I am not (yet) really used to .. It opens a few doors. Nice! Op zo 10 jun. 2018 18:20 schreef Arie van Wingerden : > ​Hi Alex, > ​ > ​ > > I would

Re: Stuck at PLEAC example

??? I can do: : (get (car Employees) 'category) -> engineer : (show (car Employees)) emp1 NIL category engineer name "Abel" -> emp1 which just works fine for me! 2018-06-10 17:43 GMT+02:00 Johann-Tobias Schäg : > > : (put emp1 'category 'engineer) > -> engineer > : (setq Employees

Re: Stuck at PLEAC example

Pls see previous reply. I don't see the need for eval here ... 2018-06-10 18:05 GMT+02:00 Johann-Tobias Schäg : > The solution to the puzzle: > (get (eval (car Employees)) 'category) > -> engineer > > Your list contain named symbols called emp1, ... , emp5 > You associate the properties with

Re: Stuck at PLEAC example

Hi Johann, you are right! In my reply to Alex I explicitly tell about that :) Thx, Arie 2018-06-10 17:31 GMT+02:00 Johann-Tobias Schäg : > You are right. But that does not change the fact that your code will > misbehave if you do not define a name. > 2. You did not mentioned mention how it

Re: Stuck at PLEAC example

Hi again, well, the master himself created the original example, so ... Also, I assume that this comparisopn might be a little bit faster, because more specific? Thx, Arie 2018-06-10 17:33 GMT+02:00 Johann-Tobias Schäg : > Also while pointer equality '== might be fine in this case '= makes

Re: Stuck at PLEAC example

​Hi Alex, ​ ​ > I would do it this way: > >(setq Employees '(emp1 emp2 emp3 emp4 emp5)) OK. You don't use the values as names, but the properties, because you'd like to refer to (: name) in the 'prinl'. Got it. >(mapc put > Employees > '(name .) > '("Abel" "Jones"

Re: Stuck at PLEAC example

Hi Johann, I think that is not correct. In the first place I think I don't need a name property. Only the 'category! In the second place: (get 'name emp1) will ALWAYS return NIL, because the function call is incorrect. It should be: (get emp1 'name) In my examples this works ok: : (put emp1

Stuck at PLEAC example

Hi Alex, I am now working on the "Arrays" section at "Find First Element that passes a Test". Your example: (with (find '((This) (== 'engineer (: category))) Employees ) (prinl "Highest paid engineer is: " (: name)) ) This won't work of course, so I created a

Re: Wiki progress

Hi, I'll have a look first and will let know! Thx, Arie 2018-06-10 7:15 GMT+02:00 Alexander Burger : > On Sun, Jun 10, 2018 at 07:04:44AM +0200, Alexander Burger wrote: > > In the DB GUI of the wiki (you get there after logging in, and going to > "My > > account"), there is a menu entry

Re: Wiki progress

corresponding css (being defined in same html file or in > extra css file): > > chaper-intro { background-color: LightCyan ; } > > example-title { color: MidnightBlue; font-family: "Arial Black"; > font-size: 20px; } > > > Greetings, Olaf > > > > > On 08

Re: Simulate EOF in terminal ...

Hi Alex, OK thx. For some examples it isn't clear how they should be run. They are not "ready to run" straight away. Since I try to make the examples approachable, I strive to also give the code (and/or data) to make such examples work. In this case I guessed that the example could use STDIN.

Simulate EOF in terminal ...

Hi, when (e.g.) executing this code in a terminal, which expects typed input, I can't manage to simulate an EOF in the terminal: (until (eof) (prinl (glue " " (flip (split (line) " " ) I know this should be possible (in Linux) by using ctrl+d. However, this forces PicoLisp to a halt!

Wiki progress

Hi, the last days I did a refresh of parts 1 .. 3 of PLEAC docs. At first I'd tried to get a nice reading experience by having lightblue backgrounds for paragraph titles and yellow backgrounds per example. Having done it that way, in the I found the reading experience far from pleasant. Also I

Re: Another PLEAC question

Hi Alex, indeed. For now I'll leave this one out and put it on a todo list. Please have a look if the rest in that section is ok! I could get hold of a copy of the Perl Cookbook and saw there that there are some useful extras for each problem. I'll add that in order to make the whole thing

Re: Another PLEAC question

Hi Alex, first I tried a GMail mail header, but that contains loads of extra stuff. Then I copied a sample header from here https://www.forensicswiki.org/wiki/Email_Headers#Sample_Header but using that doesn't show any results. Would you please check this out? It would make this section

Another PLEAC question

Hi Alex, on page http://pleac.sourceforge.net/pleac_picolisp/datesandtimes.html near the end is the program 'hopdelta'. It seems there should be some input file called 'header'. Do you have that ready or can you specify what has to go in that file? If that is done, the date and time part is

Re: Stuck on function 'expDat' on PLEAC

Oh dear! Did not see that one coming ... The issue here is that I haven't taken the time to study enough. Blush :-( Op di 5 jun. 2018 13:42 schreef Alexander Burger : > Hi Arie, > > > (at least under Windows WSL) the function 'expDat' does not seem to work > as > > expected. > > > > My

Stuck on function 'expDat' on PLEAC

Hi, working on "Parsing Dates and Times from Strings" here http://pleac.sourceforge.net/pleac_picolisp/datesandtimes.html I find that (at least under Windows WSL) the function 'expDat' does not seem to work as expected. My results: : (expDat "31") -> NIL Is this a Windows only issue?

Re: Wiki progress on PLEAC examples

Nice! Thx. Arie 2018-06-05 7:33 GMT+02:00 Alexander Burger : > Hi Arie, > > > now the first 2 parts (Strings and Numbers) are complete. > > > > Here and there I had to change things a little and also to add a few > > comments. > > Very nice, and well done! A huge piece of work. I think it looks

Wiki progress on PLEAC examples

Hi Alex, now the first 2 parts (Strings and Numbers) are complete. Here and there I had to change things a little and also to add a few comments. Sometimes it totally wasn't obvious what kind of input a function expected (at least for newcomers). Please have a look and check if things are as

Re: Another question on PLEAC docs

Great! Thx. 2018-06-03 17:23 GMT+02:00 Alexander Burger : > Hi Arie, > > > It appears to be related to rounding. > > Please explain or point me to the correct docs :) > > Please take a look at Rick Hanson's excellent explanation: > >

Re: Help needed on your soundex example

OK. The name might be a bit misleading :) Added that to the example! 2018-06-03 17:19 GMT+02:00 Alexander Burger : > On Sun, Jun 03, 2018 at 02:17:45PM +0200, Arie van Wingerden wrote: > > It was a bit of a hassle to find a nice example, but I came up with this: > > ..

Re: Help needed on your soundex example

Hi Alex, agreed. It was a bit of a hassle to find a nice example, but I came up with this: # The following example calls the native Linux function 'getenv' # in order to fetch the hostname from it (env variable = NAME). # Then it reads user input (a guess for the hostname). # Then

PicoLisp library docs

Hi, in the PLEAC docs there are a few references to functions in separate libraries. Are those library functions referenced somewhere on the web? With that I mean like this: https://software-lab.de/doc/ref.html#fun I'd like to have links to those if possible. If those reference do not exist,

Another question on PLEAC docs

Hi Alex, the results of the functions below do not reflect the common outcomes in math AFAICT. But maybe you had other intentions? E.G.: : (deg2rad 90) -> 2 Result 2 where I expected something like 1.5707963268. Any ideas? /Arie Doing Trigonometry in Degrees, not Radians

Re: Help needed on your soundex example

Hi Alex, since I notice that getpwent seems to disbehave under Windows WSL I'll leave the following out if you agree: (let (User (clip (in NIL (line T))) Code (soundex User)) (while (native "@" "getpwent" '(S S I I S S S)) # 'native' only in 64-bits (let Lst @ (when (or (=

Re: Help needed on your soundex example

Hi Alex, ah, OK!! Well, then this might be a better show off: : (soundex "Smith") -> "S530" : (soundex "Smithe") -> "S530" : (soundex "Smyithe") -> "S530" because that shows what soundex is really about, don't you think?! Also, the soundex algorith is really dependent on the language used.

Re: Wiki progress update ...

Hi Alex, thx. for taking time to check!!! I corrected those points you mention. Thx. to you too :) Because I now just try to do this stuff fast, I only have a bit of time to look at functions in more detail. I really am impressed by the many useful functions. Also nice that strings and

Help needed on your soundex example

Hi Alex, just started on the "Soundex Matching" example here: http://pleac.sourceforge.net/pleac_picolisp/strings.html It looks like a nice program, however, it doen't state what kind of input it expects :) I know about soundex, but my current knowledge of PicoLisp is not yet advanced enough.

Wiki progress update ...

The first section of PLEAC (Strings) is now at about 76% ready. Some examples are rewritten a little, in order to make it easier for people to just copy and paste the code to see what happens. I took great effort to verify each and every example. Also I added a reference to all used functions

Re: Wiki progress ...

to improve the documentation, but please be aware that you're just > adding to the confusion with this page. > > > AW > > On 05/31/2018 11:44 AM, Arie van Wingerden wrote: > > for now I added a link to your (very nice) stuff. > >

Re: Wiki progress ...

Hi Alexander, for now I added a link to your (very nice) stuff. Be assured that I intend to change stuff for the better :) Thx, Arie 2018-05-31 13:21 GMT+02:00 Arie van Wingerden : > Hi Alexander, > > you are right :-) > Because I just dived in to help and also reorder stuff, I

Re: Wiki progress ...

e (i.e: removing the > "Other resources" and "Repositories" from the Documentation page)... in > any case, the docs are quite confusing now with this additional section, > so I think it would be nice to have things a bit more organized. > > Cheers, > > >

Re: Wiki change - 'de' function 'done'

Thx. Andreas! Op ma 28 mei 2018 22:29 schreef : > Naming Conventions: https://software-lab.de/doc/ref.html#conv > > /beneroth > > Am 2018-05-28 16:54, schrieb Arie van Wingerden: > > ​Hi Olaf, > > > >> I do like your https://picolisp.com/wiki/?pcedef

Re: Wiki change - 'de' function 'done'

​Hi Olaf, > I do like your https://picolisp.com/wiki/?pcedefunction wiki page very > much! > ​Thx. You're welcome :) > > For me, it does show the subtleties of the topic in a very clear and > comprehensible way (even reproducible). > ​Nice. Reproducability is a thing I really want. Examples

Wiki progress ...

Hi all, started to put all PLEAC examples in the Wiki, inorder to preserve the material in case PLEAC vanishes sometime, because it is not updated often anymore. You could say that is was substituted in some way by the famous "Rosetta Code". Since this it quite a bit of work, I started with the

Wiki change - 'de' function 'done'

Hi all, as earlier announced, I'll try to add stuff that could be useful to others, but at least for me is a way to learn PicoLisp along the way. TL;DR; The few last days I got used to the Wiki syntax Alex created. Being at this point I find it a very easy to use Wiki, that breathes the same

Re: Understanding spacing in Wiki edit

Updated the doc. See how nice and clear the yellow is ;-)) https://picolisp.com/wiki/?pce-de-function 2018-05-26 13:41 GMT+02:00 Arie van Wingerden <xapw...@gmail.com>: > OK :) > > 2018-05-26 13:21 GMT+02:00 Alexander Burger <a...@software-lab.de>: > >> Hi Ar

Re: Understanding spacing in Wiki edit

OK :) 2018-05-26 13:21 GMT+02:00 Alexander Burger : > Hi Arie, > > > checked the source and *did* find one thing missing :-) > > > > > ("$" # CSS style > > > ( (cons 'style (till "^I^J^M}" T)) > > > (char) > > > (recurse T) ) ) > > Haha,

  1   2   >