Compilation fix for guile 1.4

Compilation fix for guile 1.4

[Davide Angelocola]

(Hi),
  I've downloaded guile version 1.4 to learn on how to program
in C under UNIX. However, when I try to compile it on my
RedHat 7.2 machine I get an error in net_db.c line 85. Well, I've 
just put a comment at the beginning of line and all works fine 
now.

Now I'm learning some guile basis but I wish a more 
user-friendly interpreter:
	o  add readline and history support
	o  add a welcome message like this:
		guile v. 	[build info?]
		Copyright 
		
		Type (help) for more information

	o  add "(copyright)", "(license)" functions
	o  the "(help)" output in one page
	o  add a TODO file in the source dist
		(this can very useful for me)

I hope that this email can be useful for you! 

Bye 
Davide Angelocola


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile

Re: Compilation fix for guile 1.4

[Thien-Thi Nguyen]

   From: Davide Angelocola <davide178@inwind.it>
   Date: Fri, 3 May 2002 13:18:23 +0200

     I've downloaded guile version 1.4 to learn on how to program
   in C under UNIX. However, when I try to compile it on my
   RedHat 7.2 machine I get an error in net_db.c line 85. Well, I've 
   just put a comment at the beginning of line and all works fine 
   now.

thanks for trying out guile.  the problem you report will be fixed in
1.4.1 and later versions.

	   o  add readline and history support

this is already available, but the documentation doesn't tell you how to
enable it (it's a documentation bug).  for now, see NEWS for more info.

	   o  add a welcome message like this:
		   guile v. 	[build info?]
		   Copyright 

		   Type (help) for more information

	   o  add "(copyright)", "(license)" functions
	   o  the "(help)" output in one page
	   o  add a TODO file in the source dist
		   (this can very useful for me)

   I hope that this email can be useful for you! 

it's useful to let us know what you want.  now that you are learning to
program, the next logical step (for both of us) is for you to learn how
to implement these requirements either by writing new code or modifying
existing code.  i would suggest looking first at the latter class of
changes since (you) going through that process would result in a patch
that could be easily applied (by us).

because the TODO file changes relatively rapidly, we publish it online,
along w/ everything else.  check out:

  http://www.glug.org/snap/workbook/tasks/TODO
  http://www.glug.org/snap/
  http://www.glug.org/

what programming experience do you have presently?  why do you want to
program in C under UNIX?

thi

_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile