postscript to lisp, plisp package error - Invalid read syntax: "#"

postscript to lisp, plisp package error - Invalid read syntax: "#"

[Henna]

This help is requested in connection with the plisp package
written by John Peterson of yale.

I am trying to use it and finding errors. I have no lucid
lisp or any other, other than the emacs lisp. I have
tried to (require 'cl) without error.


(1)
I have renamed all files in plisp to be .el from .lisp since that 
is what
emacs seems to expect. This gave more success in the next loading
command. I have also set the "load-path" variable to include both
the compiler and compiler/common-lisp directories.

(2) 
I have tried to load build.el as follows inside emacs:

(load "/home/henna/plisp/compiler/build.el") CTRL-x CTRL-e

The error I get in minibuffer is:

Invalid read syntax: "#"

Is there a simple method to solve this?
I am looking on comp.lang.postscript/lisp for help on plisp and there
is no traffic or conversation on this.

You can see the result of renaming:

% du -a
3       ./common-lisp/lisp-util.el
3       ./common-lisp/loop.el
2       ./common-lisp/mvalues.el
3       ./common-lisp/numeric.el
3       ./common-lisp/bind.el
3       ./common-lisp/control.el
2       ./common-lisp/for.el
2       ./common-lisp/functional.el
22      ./common-lisp
9       ./defps.el
2       ./flow.el
4       ./macros.el
2       ./names.el
5       ./output.el
1       ./plisp-compile.el
1       ./rename
9       ./top.el
1       ./util.el
6       ./args.el
1       ./build.el
6       ./compile.el
1       ./rename~
2       ./vars.el
1       ./t~
2       ./ps-vars.el


(3)
I loaded the file using the debugging enabled as:

(setq debug-on-error t)

and I get the following error:

Signaling: (invalid-read-syntax "#")
  eval-buffer(#<buffer  *load*<2>> nil "output")
  load-with-code-conversion("/home/henna/plisp/compiler/output.el" "output"
 nil nil)
  load("output")
  eval-buffer(#<buffer  *load*> nil "/home/henna/plisp/compiler/build.el")
  load-with-code-conversion("/home/henna/plisp/compiler/build.el"
"/home/henna/plisp/compiler/build.e$
  load("/home/henna/plisp/compiler/build.el")
  eval((load "/home/henna/plisp/compiler/build.el"))
  eval-last-sexp(nil)
* call-interactively(eval-last-sexp)


Thanks
henna@techemail.com


-=-
This message was posted via two or more anonymous remailing services.

postscript to lisp, plisp package error - Invalid read syntax: "#"

[Henna]

This help is requested in connection with the plisp package
written by John Peterson of yale.

I am trying to use it and finding errors. I have no lucid
lisp or any other, other than the emacs lisp. I have
tried to (require 'cl) without error.


(1)
I have renamed all files in plisp to be .el from .lisp since that 
is what
emacs seems to expect. This gave more success in the next loading
command. I have also setq the "load-path" variable to include both
the compiler and compiler/common-lisp directories. and checked it.

(2) 
I have tried to load build.el as follows inside emacs:

(load "/home/henna/plisp/compiler/build.el") CTRL-x CTRL-e

The error I get in minibuffer is:

Invalid read syntax: "#"

Is there a simple method to solve this?
I am looking on comp.lang.postscript/lisp for help on plisp and there
is no traffic or conversation on this.

You can see the result of renaming:

% du -a
3       ./common-lisp/lisp-util.el
3       ./common-lisp/loop.el
2       ./common-lisp/mvalues.el
3       ./common-lisp/numeric.el
3       ./common-lisp/bind.el
3       ./common-lisp/control.el
2       ./common-lisp/for.el
2       ./common-lisp/functional.el
22      ./common-lisp
9       ./defps.el
2       ./flow.el
4       ./macros.el
2       ./names.el
5       ./output.el
1       ./plisp-compile.el
1       ./rename
9       ./top.el
1       ./util.el
6       ./args.el
1       ./build.el
6       ./compile.el
1       ./rename~
2       ./vars.el
1       ./t~
2       ./ps-vars.el


(3)
I loaded the file using the debugging enabled as:

(setq debug-on-error t)

and I get the following error:

Signaling: (invalid-read-syntax "#")
  eval-buffer(#<buffer  *load*<2>> nil "output")
  load-with-code-conversion("/home/henna/plisp/compiler/output.el" "output"
 nil nil)
  load("output")
  eval-buffer(#<buffer  *load*> nil "/home/henna/plisp/compiler/build.el")
  load-with-code-conversion("/home/henna/plisp/compiler/build.el"
"/home/henna/plisp/compiler/build.e$
  load("/home/henna/plisp/compiler/build.el")
  eval((load "/home/henna/plisp/compiler/build.el"))
  eval-last-sexp(nil)
* call-interactively(eval-last-sexp)


Thanks
henna@techemail.com


-=-
This message was posted via two or more anonymous remailing services.

Re: postscript to lisp, plisp package error - Invalid read syntax: "#"

[Henrik Motakef]

Anonymous-Remailer@See.Comment.Header (Henna) writes:

> I am trying to use it and finding errors. I have no lucid
> lisp or any other, other than the emacs lisp. I have
> tried to (require 'cl) without error.
>
>
> (1)
> I have renamed all files in plisp to be .el from .lisp since that 
> is what
> emacs seems to expect.

Emacs Lisp and Common Lisp are quite different languages, and (require
'cl) is merely cosmetic. It doesn't make the languages compatible. You
won't be able to run Common Lisp programs in Emacs.

But you can simply install a Common Lisp implementation. See
<http://www.cliki.net/Common%20Lisp%20implementation> for a list of
free ones, or <http://alu.cliki.net/Implementation> for commercial
Lisps.

Re: postscript to lisp, plisp package error - Invalid read syntax: "#"

[Pascal Bourguignon]

Henrik Motakef <usenet-reply@henrik-motakef.de> writes:

> Anonymous-Remailer@See.Comment.Header (Henna) writes:
> 
> > I am trying to use it and finding errors. I have no lucid
> > lisp or any other, other than the emacs lisp. I have
> > tried to (require 'cl) without error.
> >
> >
> > (1)
> > I have renamed all files in plisp to be .el from .lisp since that 
> > is what
> > emacs seems to expect.
> 
> Emacs Lisp and Common Lisp are quite different languages, and (require
> 'cl) is merely cosmetic. It doesn't make the languages compatible. You
> won't be able to run Common Lisp programs in Emacs.

Yes you can, but it implies:
 
> But you can simply install a Common Lisp implementation. See
> <http://www.cliki.net/Common%20Lisp%20implementation> for a list of
> free ones, or <http://alu.cliki.net/Implementation> for commercial
> Lisps.

nocrew implements emacs-cl, a Common-Lisp implementation in Emacs:

http://www.nocrew.org/news.html?article=115
http://www.lisp.se/emacs-cl/

2003-12-04  Now you can run Common Lisp programs in Emacs, and write
Emacs extensions in Common Lisp.



-- 
__Pascal_Bourguignon__                     http://www.informatimago.com/
There is no worse tyranny than to force a man to pay for what he doesn't
want merely because you think it would be good for him.--Robert Heinlein
http://www.theadvocates.org/

Re: postscript to lisp, plisp package error - Invalid read syntax: "#"

[Joe Marshall]

Anonymous-Remailer@See.Comment.Header (Henna) writes:

> This help is requested in connection with the plisp package
> written by John Peterson of yale.
>
> I am trying to use it and finding errors. I have no lucid
> lisp or any other, other than the emacs lisp. I have
> tried to (require 'cl) without error.

Emacs lisp is no substitute for a real Common Lisp.

-- 
~jrm

Re: postscript to lisp, plisp package error - Invalid read syntax: "#

[Henna]

http://www.nocrew.org/news.html?article=115
http://www.lisp.se/emacs-cl/

Will it work with plisp? The following is an excerpt


http://www.nocrew.org/cgi-bin/cvsweb/cvsweb.cgi/emacs-cl/README?rev=1.23

There are problems with the cl:function macro when its output appears
in compiled files:

 * When applied to a byte-code function the result will be printed
   with the #[...] syntax.  That works, but separate invokations of
   cl:function will result in distinct, though equal, code vectors.

 * When's applied to a subr, the result will be printed with the
   #<subr ...> syntax, which will raise a syntax error when loaded.

In general, Emacs' byte compiler doesn't preserve object identity,
which is a problem.

~~~~~~~~~~~~~~~~~~~~~
If you consider the content of this post to be particularly offensive, disgusting or plain illegal,
it is probably 'designer abuse', a message designed specifically to hurt the remailer's reputation/existence.
  http://groups.google.com/groups?selm=6THHPRAL38002.4374074074%40anonymous&oe=UTF-8&output=gplain
Some people hate this remailer so badly that, for example, they did not hesitate to celebrate the death of 148 French tourists in a plane crash.
Those people seceded from the human race, so don't hesitate to report them directly to the police.
2004/01/03 (contact <abuse@cotse.com>) Blue.Jay celebrates 
  http://groups.google.com/groups?selm=Ymx1ZWpheQ%3D%3D.19d787f018eb3019d6fd3faa2125547c%401073158846.cotse.net&oe=UTF-8&output=gplain
2004/01/19 <rabbi@thetis.deor.org> Len Sassaman chooses that moment to bring his support to Blue.Jay
  http://groups.google.com/groups?selm=Pine.LNX.4.58.0401181826110.31463%40thetis.deor.org&oe=UTF-8&output=gplain

More about the subject will be available http://frogadmin.yi.org/HOS/

Re: postscript to lisp, plisp package error - Invalid read syntax: "#

[Nomen Nescio]

http://www.nocrew.org/news.html?article=115
http://www.lisp.se/emacs-cl/

Will it work with plisp? The following is an excerpt


http://www.nocrew.org/cgi-bin/cvsweb/cvsweb.cgi/emacs-cl/README?rev=1.23

There are problems with the cl:function macro when its output appears
in compiled files:

 * When applied to a byte-code function the result will be printed
   with the #[...] syntax.  That works, but separate invokations of
   cl:function will result in distinct, though equal, code vectors.

 * When's applied to a subr, the result will be printed with the
   #<subr ...> syntax, which will raise a syntax error when loaded.

In general, Emacs' byte compiler doesn't preserve object identity,
which is a problem.

Re: postscript to lisp, plisp package error - Invalid read syntax: "#"

[Golan Trevize]

Hi,

Now that is a blast from the past.
>From the subject it looks like you're looking for a PostScript to Lisp
Compiler, PLisp is a Lisp to PostScript Compiler not a PostScript to Lisp
Compiler.
It helped me years ago before I became prociient in PostScript.

Another good system that wrote quite efficient PostScript was Pdb which was
a "C to PostScript Compiler" it had a lot of uses outside NeWS.

Golan Trevize

"Henna" <Anonymous-Remailer@See.Comment.Header> wrote in message
news:Y0T9JTFR38033.4074537037@anonymous...
>
> This help is requested in connection with the plisp package
> written by John Peterson of yale.
>
> I am trying to use it and finding errors. I have no lucid
> lisp or any other, other than the emacs lisp. I have
> tried to (require 'cl) without error.
>
>
> (1)
> I have renamed all files in plisp to be .el from .lisp since that
> is what
> emacs seems to expect. This gave more success in the next loading
> command. I have also set the "load-path" variable to include both
> the compiler and compiler/common-lisp directories.
>
> (2)
> I have tried to load build.el as follows inside emacs:
>
> (load "/home/henna/plisp/compiler/build.el") CTRL-x CTRL-e
>
> The error I get in minibuffer is:
>
> Invalid read syntax: "#"
>
> Is there a simple method to solve this?
> I am looking on comp.lang.postscript/lisp for help on plisp and there
> is no traffic or conversation on this.
>
> You can see the result of renaming:
>
> % du -a
> 3       ./common-lisp/lisp-util.el
> 3       ./common-lisp/loop.el
> 2       ./common-lisp/mvalues.el
> 3       ./common-lisp/numeric.el
> 3       ./common-lisp/bind.el
> 3       ./common-lisp/control.el
> 2       ./common-lisp/for.el
> 2       ./common-lisp/functional.el
> 22      ./common-lisp
> 9       ./defps.el
> 2       ./flow.el
> 4       ./macros.el
> 2       ./names.el
> 5       ./output.el
> 1       ./plisp-compile.el
> 1       ./rename
> 9       ./top.el
> 1       ./util.el
> 6       ./args.el
> 1       ./build.el
> 6       ./compile.el
> 1       ./rename~
> 2       ./vars.el
> 1       ./t~
> 2       ./ps-vars.el
>
>
> (3)
> I loaded the file using the debugging enabled as:
>
> (setq debug-on-error t)
>
> and I get the following error:
>
> Signaling: (invalid-read-syntax "#")
>   eval-buffer(#<buffer  *load*<2>> nil "output")
>   load-with-code-conversion("/home/henna/plisp/compiler/output.el"
"output"
>  nil nil)
>   load("output")
>   eval-buffer(#<buffer  *load*> nil "/home/henna/plisp/compiler/build.el")
>   load-with-code-conversion("/home/henna/plisp/compiler/build.el"
> "/home/henna/plisp/compiler/build.e$
>   load("/home/henna/plisp/compiler/build.el")
>   eval((load "/home/henna/plisp/compiler/build.el"))
>   eval-last-sexp(nil)
> * call-interactively(eval-last-sexp)
>
>
> Thanks
> henna@techemail.com
>
>
> -=-
> This message was posted via two or more anonymous remailing services.
>
>
>
>

Re: postscript to lisp, plisp package error - Invalid read syntax: "#"

[Marco Antoniotti]

Henna wrote:
> This help is requested in connection with the plisp package
> written by John Peterson of yale.
> 
> I am trying to use it and finding errors. I have no lucid
> lisp or any other, other than the emacs lisp. I have
> tried to (require 'cl) without error.

(require 'cl) just gives you some compatibility with Common Lisp from 
Emacs Lisp.  The two dialects are quite different.

You should get one of the Common Lisp implementations off the net.  The 
sites www.alu.org or www.cliki.net are excellent starting points.


> 
> 
> (1)
> I have renamed all files in plisp to be .el from .lisp since that 
> is what
> emacs seems to expect. This gave more success in the next loading
> command. I have also set the "load-path" variable to include both
> the compiler and compiler/common-lisp directories.
> 
> (2) 
> I have tried to load build.el as follows inside emacs:
> 
> (load "/home/henna/plisp/compiler/build.el") CTRL-x CTRL-e
> 
> The error I get in minibuffer is:
> 
> Invalid read syntax: "#"
> 
> Is there a simple method to solve this?

No.  This is one of the fundamental differences between Common Lisp and 
Emacs Lisp.  Get a Common Lisp.

It will save you time and eventually it will be better.

Cheers
--
Marco