search

alandipert / gherkin

a functional programming language and interpreter written in GNU Bash 4
https://tailrecursion.com/~alan/Lisp/GherkinHistory.html
BSD 3-Clause "New" or "Revised" License
522 stars 31 forks source link

First class documentation. #34

Closed Gonzih closed 5 years ago

Gonzih commented 10 years ago

Hi, is there any plans for first class documentation? Like in clojure for example.

quoll commented 10 years ago

Clojure does it with metadata, which we don't have... not that we couldn't have it.

Gonzih commented 10 years ago

Will we have it? :)

quoll commented 10 years ago

Only if someone writes it :)

I have my own priorities, so I'll be looking at those. But it would be great if someone chose to add this feature.

twashing commented 10 years ago

+1 this request. I'm trying to figure out to i) pipe, ii) put jobs in the background, etc.

quoll commented 10 years ago

On (i) pipes and (ii) backgrounding:

i) In trying to work out what a pipe meant in Lisp terms, I decided that a list was the best model. Ideally it would be lazy, but there are other things to figure out before getting there. Consequently, the output of "sh" is a list. I saw what you'd tried on IRC, and the way I handle the same thing is to build a string out of the list and use it with "sh".

ii) There are no language bindings for backgrounding a job. I've been thinking that the best approach would be to create a fifo in /tmp for stdio on such a thing. However, I haven't had a use-case to try it out with, and I've been concerned that just implementing it for the sake of a new feature might miss something I should have done.

Meanwhile, we should probably update the wiki with these features.

twashing commented 10 years ago

Too right. That makes sense. Definitely take the time and get it right. I'm looking forward to diving more into it.

Keep it up :)

Tim Washington Interruptsoftware.com http://interruptsoftware.com

On Mon, Jan 27, 2014 at 3:49 PM, Paul Gearon notifications@github.comwrote:

On (i) pipes and (ii) backgrounding:

i) In trying to work out what a pipe meant in Lisp terms, I decided that a list was the best model. Ideally it would be lazy, but there are other things to figure out before getting there. Consequently, the output of "sh" is a list. I saw what you'd tried on IRC, and the way I handle the same thing is to build a string out of the list and use it with "sh".

ii) There are no language bindings for backgrounding a job. I've been thinking that the best approach would be to create a fifo in /tmp for stdio on such a thing. However, I haven't had a use-case to try it out with, and I've been concerned that just implementing it for the sake of a new feature might miss something I should have done.

Meanwhile, we should probably update the wiki with these features.

Reply to this email directly or view it on GitHubhttps://github.com/alandipert/gherkin/issues/34#issuecomment-33421031 .