newlispfanclub.alh.net

Hi, Lutz.

My time has suddenly been crunched. I'll return to start on QA work when I'm able.

-Noah

hi, Jeremy. Once you're happy with your code, check whether it's suitable for publishing as a part of newLISP's main module collection. Check the Perl documentation for use cases and examples of Perl-extended regex. Provide comparable use cases and examples in the documentation for your module. Cons...

Hi, Lutz. Here are some suggested edits to the newly-posted rev 13 version of the Automatic Memory Management document. -Noah - This article explains how ORO memory mangement works. + This article explains how ORO memory management works. - A ireference-counting scheme registers each allocated memor...

Hi, Lutz. Here's my first suggested edit to the Memory Management page. The edit contains two alternative paragraphs that cover the discussion of the non-use of one-bit (non)sticky counts. Let me know what's what about that; I really didn't know how to interpret the source paragraph. I attempted a g...

Hello.

Lutz, I'm half done with a first suggested edit to the Memory Management document. I started this morning, after reading your post mentioning it.

-Noah

OK, that's where I'll concentrate my efforts.

-Noah

OK.

Do you think its a good idea to include dependency information in the newLISPdoc fields? Should the newLISPdoc format include sufficient information from which to generate test suites, or is that outside the purpose of newLISPdoc?

-Noah

Hello, Lutz. What do you think about QA testing basic newLISP functionality? For example, a set of tests of newLISP functions called under normal, boundary, and error conditions. I do not have lots of time, but I can offer some time toward that effort. What do you think about module pre-installation...

Nice, tburton!

Not meaning to ignore your point.

-noah

How was the documentation included in the *.CFM files? Was it in the comments sections?

Lutz brought up the idea of embedding documentation in Javadoc-style comments in newLISP modules. He might be working on it, I don't know.

-Noah

Hi, Lutz. Here's a proposed edit. This one includes corrections to my last proposed edit. -Noah newLISP compared to Common Lisp and Scheme Last updated July 12th, 2006 This page clarifies some differences between newLISP and the older standards Common Lisp and Scheme. Read the About page to find out...

Hi, Lutz. Thank you for your helpful reply. I understand that you'd like the Difference page to read well for educated LISPers. Your example of granular argument evaluation shows CL and Scheme coders what you mean, without requiring additional explanatory text, so it would fit in well, if you want t...

Hello, Lutz. Here are some suggested edits to the "Differences_to_Other_Lisps" page. In section 1, you wrote: Like Scheme, newLISP evaluates the operator part of an expression before applying it to the arguments. Is that in contrast with Common Lisp? I'm not sure how you're identifying a difference ...

Hi, Everybody. For anyone who's interested in more postscript stuff, the Developer SDK is available. Check out the Postscript books available for free as well. The so-called Blue Book is a great starting point (exactly where I'm at). You'll have to agree to the license agreement to download the SDK ...

Hello.

Here's another suggested edit: -Noah

Hello, Lutz. It looks like you've made a round of changes to the homepage. Here is a second round of suggested edits to the new homepage content. The first sentence on the page can be edited for syntax and grammar, and also for writing style. Here is a suggested edit to its syntax and grammar: - new...

Hi, Lutz. Here are some suggested edits to the homepage. The parenthesis-enclosed + diffs are deeper edits, but they might be technically inaccurate or otherwise unsuitable. -Noah -newLISPtm for BSDs, GNU/LINUX, MacOS X, Solaris, Win32 +newLISPtm for BSD, GNU/LINUX, OS X, Solaris, and Win32 -newLISP...

Hi, Lutz. You wrote that you wanted C libraries that support complex numbers. The documentation for the gnu C library, libc, mentions support for complex number types, arithmetic, and the additional functions conjugation, projections, and decomposition of complex numbers. The math functions like sin...

Hello, Lutz, Jeremy. I'm hoping that a means is made available for uploading modules, categorizing them, generating their documentation on-line, and making them available for newLISP programmers to search, read, and download. This means would function like CPAN or CTAN . It would archive modules on-...

Hello, Lutz. I'm glad my prior effort was helpful to you. Here are additional suggestions for grammar/spelling edits to make to the revised 'About' webpage. -Noah - It has all of the essential elements that made LISP famous: 'symbol processing, lists, anonymous functions (lambda expressions), and S-...

Hello, Lutz. Here's a second attempt at my edit, with privately-sent patches from Michael. He's very thorough. Lutz, would you please note that Cormullion's suggestion to divide Question 17 into two question-answer pairs requires me to perform a technical edit rather than a grammar/spelling edit. I'...

Hi, Cormullion. I tried to stay true to the basic writing style and FAQ structure that appeared on the original webpage, so changes of the kind you suggest were off my screen. I actually found some punctuation errors and a couple grammatical errors in my posted edit. This was a quick edit - it was f...

Hello, Lutz. Reading over the 'about' webpage, I noticed a few spelling errors. Putting the webpage content into MS Word made it easy for me to correct those, but then I got carried away. For what's it's worth, here's what I produced. Let me know if you'd like a version with just spelling errors cor...

Hi, Lutz. I'll be reading How to Write Doc Comments For the Javadoc Tool . newlispdoc looks good, too.Ship it with newlisp, and programmers will use it. What's most exciting about this is how it will bring newlisp modules into the spotlight. Adding on a unified documentation system for them that's r...

Hello. Thank you, Lutz, for your thoughtful reply. Another documentation option is to add embedded documentation built-ins to newLisp. For example: (doc:section (head "Hello World Program") (para "This program prints out (i "Hello, World")) ) (print "Hello, World") newLisp could work like Perl does ...