security-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [security-discuss] GFDL holds the answer about fancy javascript (was


From: Alfred M. Szmidt
Subject: Re: [security-discuss] GFDL holds the answer about fancy javascript (was: gnuradio project..)
Date: Mon, 06 Mar 2017 01:37:20 -0500

   >   > I was reviewing this link of documentation, and could not
   >   > find any relation to a license:
   >   > http://gnuradio.org/doc/doxygen/index.html
   > 
   > Can you find the source code for this in the source repo?
   > 
   >   > However, documentation within the package
   >   > gnuradio-3.7.10.1.tar.gz is
   > 
   > Is that the source code of the documentation in
   > http://gnuradio.org/doc/doxygen/index.html?
   > 
   > I am guessing that you already know the answer, but I don't -- I
   > have never seen either of them.

   Source code is in gnuradio-3.7.10.1/docs/doxygen/other, if I am no
   mistaken.

   And GNU radio package is to be found here:
   http://gnuradio.org/releases/gnuradio/gnuradio-3.7.10.1.tar.gz

   Source code of documentation is not in simple format, it seems to
   be Doxygen format. Doxygen extracts documentation from C++ files.

What is "simple format"?

There are two parts to the documentation in GNU radio, one is the .dox
files and the other is inline source code documentation in the ñthe
C/C++/Python/etc source files.

The .dox files seem to make up the bulk of the manual consisting of
the "User Manual", the various parts of GNU radio, and what not and
are scattered around in various doc/ directories.  While the source
code files contain the API reference.

Examples, this is API documentation extracted from a source code file:

  http://gnuradio.org/doc/doxygen/classgr_1_1feval__dd.html

the source for that is in

        gnuradio-runtime/include/gnuradio/feval.h.

While the soruce code for

        http://gnuradio.org/doc/doxygen/page_components.html 

lives here:

        ./docs/doxygen/other/components.dox



reply via email to

[Prev in Thread] Current Thread [Next in Thread]