Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot

Re: Lisp to Perl compilation

by hding (Chaplain)
on Jan 16, 2004 at 03:21 UTC ( #321730=note: print w/replies, xml ) Need Help??

in reply to Lisp to Perl compilation

I can't get to your website, so it's hard to say, but it could be interesting. Especially if one could use it to write Lisp but leverage the power of CPAN, for example. Being a Common Lisp person myself I can't especially say that I care for it being Schemish, but it's your baby. :-)

Replies are listed 'Best First'.
Re: Re: Lisp to Perl compilation
by hhdave (Beadle) on Jan 16, 2004 at 08:38 UTC

    Thanks to others for correcting my URL.

    Being able to leverage the power of CPAN was one of my reasons for doing it (though I've only just implemented a way of calling perl methods). Plus things like perls great regex support. Since I've started playing with Lisp I've decided I really like it. In particular I think macros are fantastic. It implements common lisp like (defmacro ...). In fact, that is how most of it is implemented.

    If you want it to be more common lisp like (2 namespace, and other stuff) you can easily achieve that by redefining (and adding to) some of the core macros. There's a macro (*FCALL*) which is expanded to do ordinary function calls. If you wanted to help trying to get it to be more compatible with common lisp (maybe as a 'compiler personality' or something) that would be cool

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://321730]
[choroba]: No, if there are no threads, then the user wants to use MCE. If there are threads, the user can choose.
[1nickt]: choroba Understood. I'm wondering about the logic in a cpanfile. If the perl doesn't support threads, it's easy: require MCE. If the perl does support threads, as you say the user has a choice, so require both? Or, assume that irrespective of the choide
[1nickt]: ... choice, the threaded-perl user *probably* wants to use threads, therefore only require threads and leave MCE out, allowing the user to manually install if desired?
[choroba]: just require any of MCE and threads. Not sure if that's possible in the cpanfile, but should be possible early in the Makefile
[1nickt]: The app expects threads as default anyway, right?
[choroba]: that's true
[1nickt]: expects threads *to be* the default
[1nickt]: I think cpanfile can handle the logic. testing now.

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (12)
As of 2017-10-18 13:20 GMT
Find Nodes?
    Voting Booth?
    My fridge is mostly full of:

    Results (244 votes). Check out past polls.