nuweb-users — nuweb users discussion list

Re: [Nuweb-users] Re: Nuweb questions, concerns

[Serge W. <se...@tu...>]

On Thu, 28 Mar 2002, M. Wroth wrote:

> There's a larger class of tools that are "language aware"; my personal
> favorite is FWEB, which deals with FORTRAN, RATFOR, C, TeX (more or less),
> and has a verbatim mode.

Which Fortran? 77? 90? 95?

> >1) The tar of nuweb plops the source in the current directory (this is
> >easy to fix) and the Makefile didn't include an installation procedure.
>
> Put the executable somewhere on the system path (or create an appropriate
> alias)

Why was this decision made to do it this way in the first place is what
I'm asking.

> The usage is simple enough that I picked it up from the manual; a secondary
> item is the source itself, which is written in nuweb.

I didn't. Maybe becuase I'm so unfamiliar with these literate programming
tools, but I didn't really understand the manual without a larger context.

Keep in mind I don't know the other WEBs.

By the way, I was also wondering if nuweb was Python clean.
That is, will it work with Python since Python is space deliminated?

- Serge Wroclawski

[Nuweb-users] Re: Nuweb questions, concerns

[M. W. <ma...@as...>]

>
>Message: 1
>Date: Thu, 28 Mar 2002 09:40:40 -0500 (EST)
>From: Serge Wroclawski <se...@tu...>
>To: <nuw...@li...>
>Subject: [Nuweb-users] Nuweb questions, concerns
>
>Hello,
>
>I was looking at literate programming tools and as I began my
>"evaluation", I came to the following conclusions:
>
>WEB / CWEB :  Very powerful, limited to thier languages and requires TeX
>               (not LaTeX)

There's a larger class of tools that are "language aware"; my personal 
favorite is FWEB, which deals with FORTRAN, RATFOR, C, TeX (more or less), 
and has a verbatim mode.

>NoWEB : Powerful, but requires icon, meaning it's not portable
>
>
>A friend recommended nuweb. I liked what I heard. It's in a pretty simple,
>cross platform C and has useful additions for HTML. Immediately, though, a
>few problems/questions  have come up, and I'm hoping that people here can
>address them:
>
>1) The tar of nuweb plops the source in the current directory (this is
>easy to fix) and the Makefile didn't include an installation procedure.

Put the executable somewhere on the system path (or create an appropriate 
alias)

>2) There's no tutorial for nuweb, only reference material

The usage is simple enough that I picked it up from the manual; a secondary 
item is the source itself, which is written in nuweb.

>3) I can't tell if there's any active development on it.

Not so you'd notice.  OTOH, it's a pretty robust and stable code that does 
its job.

There is one fix needed for Windows machines ... but that's simple enough 
that even I could figure it out.

Mark B. Wroth
<ma...@as...>

[Nuweb-users] Nuweb questions, concerns

[Serge W. <se...@tu...>]

Hello,

I was looking at literate programming tools and as I began my
"evaluation", I came to the following conclusions:

WEB / CWEB :  Very powerful, limited to thier languages and requires TeX
	      (not LaTeX)

NoWEB : Powerful, but requires icon, meaning it's not portable


A friend recommended nuweb. I liked what I heard. It's in a pretty simple,
cross platform C and has useful additions for HTML. Immediately, though, a
few problems/questions  have come up, and I'm hoping that people here can
address them:

1) The tar of nuweb plops the source in the current directory (this is
easy to fix) and the Makefile didn't include an installation procedure.

2) There's no tutorial for nuweb, only reference material

3) I can't tell if there's any active development on it.


Am I missing something?

Thanks,

- Serge Wroclawski

[Nuweb-users] Re: Nuweb-users digest, Vol 1 #13 - 1 msg

[Marc W. M. <me...@fn...>]

"Ioffe, Robert" wrote:
> It seems some of the links on http://nuweb.sourceforge.net/ web-site still
> point to the old documents:
>
> nuweb.w points to 0.93 version
> The first postscript link points to 0.94 version.

I fixed the nuweb.w link (actually I removed it, and made a link to
the SourceForge download page, since they don't want distribution
done via the webpage...)

However the file the postscript link points to *was* updated. Perhaps
a browser cache flush is in order?

> Thanks for an excellent tool.

Thanks for the note!

Marc

[Nuweb-users] Please update all the documents on the nuweb website

[Ioffe, R. <rob...@in...>]

Hi,

It seems some of the links on http://nuweb.sourceforge.net/ web-site still
point to the old documents:

nuweb.w points to 0.93 version
The first postscript link points to 0.94 version.

Please correct it.

Thanks for an excellent tool.

Robert

Re: [Nuweb-users] a compilation warning

[M. W. <ma...@as...>]

It's been a while since I tried to compile Nuweb, and even longer since I 
did it with GCC.  Using tempname did indeed cause a problem on my (Windows) 
machines, and I was running into trouble with GCC truncating filenames to 
8.3 uppercase.  Switching compilers solved the later problem, but I had to 
change the code for the former.

At 12:08 PM 1/13/02 -0800, you wrote:
>From: "Nick van Foreest" <no...@ho...>
>To: nuw...@li...
>Date: Sun, 13 Jan 2002 19:12:56
>Subject: [Nuweb-users] a compilation warning
>
>Hi,
>
>I compiled nuweb 0.93 on my machine, but got the following (not crucial)
>warning:
>
>
>chuck:/home/nicky/programs/nuweb>> ls
>nuweb.w
>chuck:/home/nicky/programs/nuweb>> nuweb nuweb.w
>nuweb: you'll need to rerun nuweb after running latex
>chuck:/home/nicky/programs/nuweb>> gcc *.c
>/tmp/ccM8RLIl.o: In function `write_files':
>/tmp/ccM8RLIl.o(.text+0x3d): the use of `tempnam' is dangerous, better use
>`mkstemp'
>chuck:/home/nicky/programs/nuweb>>
>
>My c compiler is gcc-2.95.
>
>bye
>
>Nicky

Mark B. Wroth
<ma...@as...>

[Nuweb-users] a compilation warning

[Nick v. F. <no...@ho...>]

Hi,

I compiled nuweb 0.93 on my machine, but got the following (not crucial) 
warning:


chuck:/home/nicky/programs/nuweb>> ls
nuweb.w
chuck:/home/nicky/programs/nuweb>> nuweb nuweb.w
nuweb: you'll need to rerun nuweb after running latex
chuck:/home/nicky/programs/nuweb>> gcc *.c
/tmp/ccM8RLIl.o: In function `write_files':
/tmp/ccM8RLIl.o(.text+0x3d): the use of `tempnam' is dangerous, better use 
`mkstemp'
chuck:/home/nicky/programs/nuweb>>

My c compiler is gcc-2.95.

bye

Nicky



_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com

[Nuweb-users] Re: Nuweb-users digest, Vol 1 #9 - 1 msg

[M. W. <ma...@as...>]

Not a nuweb issue: nuweb passes the Latex through unchanged.  The problem 
is that you are using a "\documentstyle{}" command for your document, not a 
"\documentclass{}" command. Fix that and this error should go away.




From: hughmyers <hug...@mi...>
>To: "'nuw...@li...'"
>         <nuw...@li...>
>Date: Fri, 7 Sep 2001 14:53:01 -0600
>Subject: [Nuweb-users] Not yet LaTeX2e Yet?
>
>I keep seeing:
>
>          Entering LaTeX 2.09 COMPATIBILITY MODE
>  *************************************************************
>     !!WARNING!!    !!WARNING!!    !!WARNING!!    !!WARNING!!
>
>  This mode attempts to provide an emulation of the LaTeX 2.09 [....]

Mark B. Wroth
<ma...@as...>

[Nuweb-users] Not yet LaTeX2e Yet?

[hughmyers <hug...@mi...>]

I keep seeing:

         Entering LaTeX 2.09 COMPATIBILITY MODE
 *************************************************************
    !!WARNING!!    !!WARNING!!    !!WARNING!!    !!WARNING!!   
 
 This mode attempts to provide an emulation of the LaTeX 2.09
 author environment so that OLD documents can be successfully
 processed. It should NOT be used for NEW documents!
 
 New documents should use Standard LaTeX conventions and start
 with the \documentclass command.
 
 Compatibility mode is UNLIKELY TO WORK with LaTeX 2.09 style
 files that change any internal macros, especially not with
 those that change the FONT SELECTION or OUTPUT ROUTINES.
 
 Therefore such style files MUST BE UPDATED to use
          Current Standard LaTeX: LaTeX2e.
 If you suspect that you may be using such a style file, which
 is probably very, very old by now, then you should attempt to
 get it updated by sending a copy of this error message to the
 author of that file.
 *************************************************************

I'm running 0.87b. I wonder if 0.92 attends to this problem.

thanks
hsm

[Nuweb-users] RFE for Nuweb

[MARK.WROTH@Aerojet.com (W. Mark)]

I don't know if anyone is considering a new release of nuweb, but I have
a few things that I'd like to throw out for consideration if anyone is.

"Bug" fix


   *     The unmodified code is not very happy on Windows systems, due
     to the file comparison routine.  A patch for this is simple (in
     scrap 41b, some substitute for temp_name is needed); a generally
     portable solution would be useful.

Thoughts for potential enhancements (possibly creeping featureitis :-)
for nuweb.

  1. Allow a scrap body in running text (e.g. this is text referring to
     the variable @{foo@}.  This would presumably be set in verbatim
     mode, but would also be scanned for inclusion of foo in the @u
     index.  The same effect could be achieved (somewhat less
     conveniently) by defining a new scrap type, say @v@{foo@}, or a new
     delimiter, say @+foo@+.
  2. Allow inversion of the usual indexing behavior; allow me to provide
     a list of strings not to index, and include all strings not in that
     list in the @u index.

After using nuweb pretty intensively for several years, these are the
only significant changes I'd like to make.  So I'm very pleased with the
program; these fall in the area of conveniences, not problems.

[Nuweb-users] Re: Nuweb-users digest, Vol 1 #6 - 1 msg

[<mar...@us...>]

>
>On Mon, 5 Feb 2001 nuw...@li... wrote:
>> 
>> Are you aware of an old port of nuweb, called aminuweb?
>
>No, I was not familiar with it.  Do you still have a pointer to it
>handy?  Otherwise I can go surfing around for it.  I would be happy
>to try to roll in such changes; allthough my time to  work on it is
>scarce.
>
Aminuweb is on ctan and mirrors, e.g.:
ftp://ftp.ntg.nl/pub/tex-archive/web/nuweb/nuweb_ami/

further succes,

Marc

[Nuweb-users] Re: Nuweb-users digest, Vol 1 #6 - 1 msg

[Marc W. M. <me...@fn...>]

On Mon, 5 Feb 2001 nuw...@li... wrote:
> 
> recently I saw the newer versions of nuweb on sourceforge.  I would
> like to draw your attention to the following:

I noted them as a bug report, I'll get around to them, really.

> Thanks that you are working further on nuweb.  Is there a history of
> differences between the different versions of nuweb?

I believe the CVS Repository on sourceforge has everything I know
of, you can browse it on the web at:
 http://cvs.sourceforge.net/cgi-bin/cvsweb.cgi/?cvsroot=nuweb
The cvsweb browser does really excellent color-coded side-by-side diffs
between versions.
I first picked it up from Preston at verision 0.87b.

Pretty much everything is of course in the one nuweb.w file, so
it's revision history is pretty much the whole thing.

> Are you aware of an old port of nuweb, called aminuweb?
> From the readme:
> 
> "Concerning the use of NUWEB with other human languages than English, I
> implemented full localization of all strings used for terminal output as
> well as LaTeX output for the Amiga version of NUWEB only.  Should someone
> create translations for other languages as well, I would appreciate to
> receive a copy for inclusion in future distributions."

No, I was not familiar with it.  Do you still have a pointer to it
handy?  Otherwise I can go surfing around for it.  I would be happy
to try to roll in such changes; allthough my time to  work on it is
scarce.

Marc Mengel <me...@fn...>

[Nuweb-users] nuweb manpage + questions

[<mar...@us...>]

Hi Marc and Charles,

recently I saw the newer versions of nuweb on sourceforge.  I would
like to draw your attention to the following:

in the man page:

the command line options:

-v verbose

and 

-n Forces scraps to be numbered sequentially from (instead of using
 page numbers), better for multipage scraps.

are missing


under format of nuweb files the following misses:


@<macro-name@>  inside a scrap, invoke a macro



Thanks that you are working further on nuweb.  Is there a history of
differences between the different versions of nuweb?


Are you aware of an old port of nuweb, called aminuweb?
From the readme:

"Concerning the use of NUWEB with other human languages than English, I
implemented full localization of all strings used for terminal output as
well as LaTeX output for the Amiga version of NUWEB only.  Should someone
create translations for other languages as well, I would appreciate to
receive a copy for inclusion in future distributions."



yours

Marc

mar...@us...

[Nuweb-users] Re: Nuweb-users digest, Vol 1 #4 - 1 msg

[Marc W. M. <me...@fn...>]

> Date: Fri, 02 Feb 2001 08:51:59 +0100
> 
>      sh...@he... 
> 
> This was my wife's email address, and she does not use it anymore. Can
> you change it to my name? 
> 
> Nicky van Foreest
> n.d...@ma...

Nicky,

I would be happy to.  Good to hear from you again!

Marc

[Nuweb-users] nuweb: name

[N.D.vanForeest <n.d...@ma...>]

Hi Marc,

Refering to this line in the nuweb document:

Since maintenanc has been taken over by Marc Mengel, online
contributions have been made by: 

     sh...@he... 



This was my wife's email address, and she does not use it anymore. Can
you change it to my name? 

Nicky van Foreest
n.d...@ma...

As such anybody could claim to be the owner of the above non-existent
email address. However, I can tell that I added the @% command to quote
out (parts of) scraps. Hopefully this is enough to convince you about my
being the author. If not, so be it.

bye

Nicky

[Nuweb-users] Re: noweb & nuweb (Albert Wagner)

[Marc W. M. <me...@fn...>]

On Mon, 15 Jan 2001 Albert Wagner <alw...@tc...> wrote:
> 
> I have just started exploring literate programming and am confused about
> the difference between nuweb and noweb.  Could someone clarify for me?
> 

Well, they're completely distinct programs, with sligthtly different
philosphies:

* "noweb", I believe, is a multi-language literate programming
  tool, with filters to pretty-print different languages.  I haven't
  done much with noweb; so my appreciation of it is somewhat vague.

* "nuweb" is a language-independant tool, with *no* automatic pretty-
  printing of  programming languages, (although recent changes allow
  limited user-directed markup of code, and allow code fragments which
  happen to be TeX to be typeset rather than presented as TeX source).

I believe nuweb is signifigantly faster; while noweb's processing time
can vary greatly depending what languages and filters are being used.

I believe nuweb, on the other hand, makes much prettier source code
listings of C code (for example) without explicit user-directed markup
strings being added to the code.

Hope that helps,

Marc Mengel <me...@us...>

[Nuweb-users] noweb & nuweb

[Albert W. <alw...@tc...>]

I have just started exploring literate programming and am confused about
the difference between nuweb and noweb.  Could someone clarify for me?

[Nuweb-users] nuweb 0.91 on Windows/Linux & some extensions

[<fsu...@hp...>]

Hi,

  I'm Francesc Subirada and I'm new to literate programming. Now I'm
facing a new project & we have to setup 'quickly' the developement
environment. One of the needs for it is that shoulb be cross-platform
among Windows, Linux ( as primary platforms ) & generic Unix. As
documentation is very important for us, we thought to use literate
programming as first approach & we've choosen 'nuweb' as our tool
because its portability & simplicity.

I've got your 'tar' distribution file for nuweb 0.91. I've decompress 
it and also I've  download the 'nuweb.w' file from the nuweb page and 
they are not the same size. Do you know why ? Which one is the correct
one ?. By the way, both seems to work so ...

As told before,I also must have the same tools on Windows than in 
Linux/Unix so I'd want to compile it in windows platforms. In order to 
do that I've make a modified makefile (makefile.bcc) in order to use
the Borland compiler (bcc32.exe). After some work I've got it working
but I've had to change the way the temporary file names are created.
On the 'output.c' file , the function 'write_files' I've change:

      char *temp_name = tempnam(".", 0);

which is making memory exceptions on windows by:
      
      char temp_name[255];
      strcpy(temp_name,".");
      strcat(temp_name,files->spelling);
      strcat(temp_name,".tmp");

which is not.  Now it's working.

   Also when trying to rebuild the documentation from the TeX file, 
it's missing some bibliography files (the 'litprog' & the 'master').In
order to regenerate the documentation properly I've rebuild it using the
printed documentation (more or less).

  I've begin to play with the nuweb file, in order to learn more about
literate programmin. One thing that our team would like is some degree
of pretty printing (similar to syntax highlighting) but just as an
optional feature. I've begin to investigate and learn about the nuweb 
code and finally I've modified it to allow making simple pretty printing
using the latex 'listings' package (which is not totally free, but
almost).

    I've modified the source to include the '-l' option which will
replace the standard verbatim (\verb) environment by the listing
environment included in latex, which is able to produce and control 
code pretty printing. The package inclusion & configuration must be 
done by the user (basically substitutes the \verb command by the
\lstinline command).An overview of the changes is:
	
	- On the global.h file add the 'listing_flag' to the extern 
         variables.
	- On the global.c file add the 'listing_flag' to the variables.
	- On the main.c add the -l option , include some more help and
	 add some end-of-line to make windows printing OK. And also 
	 I've included command help.
        - On the latex.c file I check if the listing_flag is TRUE. In
	 that case I substitute the \verb by \lstinline	

  Finally I've made some modifications to the LaTeX commands in order 
to configure & load the listings package and also include some extra
commands to improve the generation of PDF using pdfTeX (for us, the PDF
documentation is also really important). And ,of course, update the
documentation to get all the information about the '-l' switch.

   This has been my first experience (and a very good one!) with
literate programming and also my first contribution to a project. I
don't know how you expect the contributions, that's why I've even
modified the source to make the documentation match the code (thus
'generating' a 0.92 release). I've done that in order to have an
internal working & 'standard' code & documentation to distribute among
our team to begin testing & working. I'd expect you will introduce that 
change in the main code, ad when you'll do that I'll substitute the
internal 0.92 release (I'm just going to distribute it internally).
Actually the listings package supports a lot of languages:

	Ada, Algol,C (ANSI,Objective), Cobol (1985,1974,ibm),
	Comal 80, C++ (ANSI,Visual), csh, Delphi, Eiffel, Elan,
	Euphoria, Fortran (95,90,77), IDL, HTML, Java, Lisp, 
	Logo, Matlab, Mercury, Modula-2, Oberon-2, 
	Pascal (Standard,XSC,Borland6), Perl, PL/I, Prolog, 
	Simula (67,CII,DEC,IBM), SQL, TeX (plain,primitive,LaTeX,
	allLaTeX), VHDL

and I'll add Python at this list. The drawback is that the document
generation is SLOOW. It has a lot of flexibility (if you want to use it)
and a fairly good defaults.

  The file attached are:

	> nuweb0.91a.tar.gz
	  This is your original tar file for the 0.91 release just
	making the change to compile it in windows with borland bcc32.

	The included files are your original ones plus:
		- nuweb.w 	=> changed as specified.
		- nuweb.exe	=> windows binary version.
		- nuweb		=> Linux binary version.
		- *.pdf		=> documentation generated using pdfTeX
		- makefile.bcc	=> Makefile for windows Borland bcpp32
				free compiler, fpTeX & cygwin tools.
		- makefile.ux	=> Original nuweb Makefile
		- makefile.lnx	=> Makefile for Linux , teTeX & gnu
				tools

	> nuweb0.92.tar.gz
	  This is the 'internal' 0.92 release I've generated.

	Files:	makefile.bcc	=> Makefile for windows Borland bcpp32
				free compiler, fpTeX & cygwin tools.
		makefile.ux	=> Original nuweb Makefile
		makefile.lnx	=> Makefile for Linux , teTeX & gnu
				tools
		nuweb.exe	=> nuweb executable for windows.
		nuweb		=> Linux executable
		*.c *.h		=> sources for nuweb rev. 0.92
		nuweb.pdf	=> PDF documentation for all nuweb 0.92
		nuwebdoc.pdf	=> PDF user guide documentation.
		nuweb.w		=> nuweb WEB file for rev. 0.92
		*.tex		=> LaTeX original documentation.
		*.bib		=> BibTeX bibliogrphies.

	   NOTE: The documentation here is pretty printed.

  I hope that will help. In fact I have several ideas to make better PDF
& may be introduce a simple syntax highlighting (like vim / Emacs).
  
Regards,

Francesc Subirada

P.S. I'll have to do it fairly fast, so if you can tell me which is the
best way to send you my contributions I'll be very glad t make it.