I get the following on the latest from arc-wiki (Tue Feb 26 10:33:26 PST 2008):
Use (quit) to quit, (tl) to return here after an interrupt.
arc> (defop hello req (pr "hello world"))
#<procedure:gs1657>
arc> (asv)
The syntax of the command is incorrect.
ready to serve port 8080
'uname' is not recognized as an internal or external command,
operable program or batch file.
make-string: expects argument of type <non-negative exact integer>; given -1
=== context ===
cut
date
memodate
srvlog
gs1078
handle-request-thread
The first time you clone the repository with "git clone," you'll be fully up-to-date until someone pushed something else. Then you can use "git pull" to grab that.
I saw, that's how I was able to test. Thank you for setting it up, by the way! And if you fixed it, thank you for that; if someone else did, thank them for that.
So someone usefully adds docstrings to the OpenID code in Anarki, and when I push my next version I'd need to be dealing with code that has docstrings in it.
I think it's perfectly fine that Anarki prefers to have its documentation in docstrings. I welcome anyone who wants to to add the OpenID code to Anarki to do so (it's in the public domain, after all). If you had said, "can I add this to Anarki", I'd say "sure, I'd be delighted". If there are any patches that would help make my code easier to incorporate into your distribution, I'd be happy to consider them.
But your question was "could you add it to Anarki". The answer is no, I'm not going to take the time to be a downstream maintainer for code in a distribution that has conventions that I don't like. In fact, I'm not sure I'd become a downstream maintainer of code in a distribution that I did like.
Everyone, every single person, has exactly the same amount of time. We all have 24 hours in the day. We all have different goals, different desires. If someone out there likes the direction Anarki is going in and thinks this OpenID code I wrote is useful and wants to spend some of the limited time they have to add it to Anarki, I'm delighted. More power to you, whoever you are.
And if no one wants to take the time to do that, that's OK with me too! :-)
I don't suppose you'd be willing to put your OpenID stuff in a git fork of the Anarki official branch, then? The official branch is just arcn.tar, and it would allow us to easily share patches back and forth.
If you need hosting, I have more GitHub invites than I know what to do with.
I am in fact leaning towards basing my projects on your new stable branch. arcn + bug fixes sounds like a good place to build upon ^_^ Plus I could see myself cherrypicking particular functionality that I want from the wiki.
I did my first commit using git ever this morning pushing the atomic-invoke bug fix to the stable branch... let me know if I did everything in the right way in terms of the log message and so on; I know nothing about what typical git project conventions are.
I assume that once I read some more of the git tutorials I'll discover I can easily publish at least a read-only copy of my git repository off of my web site, yes?
Forgive my newbness but I've not used git before and don't really have a clue where to start. I did read that you can connect to git repos with other clients (I currently have TortoiseSVN installed) and would love to know how to do that as it would probably be the easier than setting up cygwin and figuring out git. Any help would be appreciated.
You can use git as a frontend to an svn repo but I haven't heard about doing it the other way. Because git is a superset of svn it may be possible but a quick search turns up nothing. Setting up cygwin is a snap. I am still a git noob. After an hour or two of reading you'll be able to use the git basics and after a few hours more reading you'll be able to use the basics and actually know wtf is going on underneath.
Please follow the Anarki conventions. Don't use hard tabs, format your code properly, use descriptive commit messages, and don't clobber other people's improvements without a reason (in this case, the lset special form).
I've pushed fixes for the formatting/tabbing and lset issues.
Also, what if the explicitly-unhygienic macros want to have some hygiene? By this I mean that, for example, if you make "aif" totally unhygienic, more than just "it" gets exposed. "@if" is in no way a black box - you also need to be concerned about shadowing "let", "car", etc.
