q-lang-users Mailing List for Q - Equational Programming Language (Page 12)
Brought to you by:
agraef
Menu
▾
▴
q-lang-users — general discussion, questions, suggestions, etc.
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(3) |
Feb
(27) |
Mar
|
Apr
(4) |
May
(11) |
Jun
(5) |
Jul
(5) |
Aug
(6) |
Sep
(15) |
Oct
(28) |
Nov
(8) |
Dec
|
| 2005 |
Jan
(9) |
Feb
(5) |
Mar
(10) |
Apr
(43) |
May
(8) |
Jun
(31) |
Jul
(45) |
Aug
(17) |
Sep
(8) |
Oct
(30) |
Nov
(2) |
Dec
(6) |
| 2006 |
Jan
(4) |
Feb
(20) |
Mar
(1) |
Apr
|
May
(92) |
Jun
(179) |
Jul
(26) |
Aug
(65) |
Sep
(36) |
Oct
(38) |
Nov
(44) |
Dec
(68) |
| 2007 |
Jan
(11) |
Feb
(25) |
Mar
(37) |
Apr
(7) |
May
(83) |
Jun
(77) |
Jul
(44) |
Aug
(4) |
Sep
(28) |
Oct
(53) |
Nov
(12) |
Dec
(21) |
| 2008 |
Jan
(66) |
Feb
(45) |
Mar
(30) |
Apr
(50) |
May
(9) |
Jun
(18) |
Jul
(11) |
Aug
(6) |
Sep
(4) |
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
|
From: Rob H. <hub...@gm...> - 2007-11-15 09:51:36
|
Hello Albert, > NB, Rob: This isn't quite the Q+Q/Q[i][X] calculator program I promised > a while ago, but it should be even better-suited for that purpose. :) It sounds good so far. As you know, with me being a lazy Windoze user, I tend to wait for the pre-built Windows installer to be made available. > But maybe it would be useful to work on ratutils.q and polynomial.q, in > order to provide more "QCalc-friendly" frontends for some of the > operations of these modules? If you're interested, please get in touch > or post to the ml. Probably. However, I wouldn't want you waiting for me, as I am finding very little time to use the home PC for my own projects at the moment. I've not touched any Q code for some months now unfortunately. Is there any draft documentation I could read yet, or a rough spec of what is required? Thanks, Rob. |
|
From: Albert G. <Dr....@t-...> - 2007-11-13 12:08:55
|
> For your convenience, I've also uploaded a current cvs snapshot. You can > find that here: RC3 is now available from the same spot, and has also been tagged as R1_0_RC3 in cvs. This has a *lot* of bugfixes and improvements, and cells spanning multiple rows and columns are now also supported (see the new Merge cells and Dissociate cells operations in the Edit menu). Albert -- Dr. Albert Gr"af Dept. of Music-Informatics, University of Mainz, Germany Email: Dr....@t-..., ag...@mu... WWW: http://www.musikinformatik.uni-mainz.de/ag |
|
From: Albert G. <Dr....@t-...> - 2007-11-10 11:06:50
|
Hi again, this just in from our "nifty and experimental new stuff" department, for those of you who like to live on the bleeding edge. :) There's a new QCalc application, which is a spreadsheet-like frontend to the Q interpreter. This is currently only available in cvs, and is still being worked on, but the revisions tagged as R1_0_RCn (where n=1,2 currently) should already be usable. Preliminary documentation (including screenshots) can be found here: http://q-lang.sourceforge.net/qcalc/qcalc.html Note that this program needs Qt/Q 1.2 (Qt3 has been tested, Qt4 probably needs some work). Bug reports and patches are appreciated. You can find the cvs sources here: http://q-lang.cvs.sourceforge.net/q-lang/qcalc/ For your convenience, I've also uploaded a current cvs snapshot. You can find that here: http://sourceforge.net/project/showfiles.php?group_id=96881&package_id=251927 (That tarball is rather big, as it also contains the docbook'ified online documentation and the complete Q language manual. If you go with the cvs sources you'll have to generate the documentation using 'make', which requires docbook and texinfo.) I think that this application is a real killer, as it makes using Q so much more convenient, and it also has the potential to eventually replace QPad on Windows, as soon as Qt/Q has been ported there and the remaining portability issues have been sorted out. I also have plans to add more support operations (the stuff in calclib.q) for graphics and multimedia, which would turn QCalc into a kind of crossover of Excel and Ableton Live on steroids. Eddie Rucker has already been working on some mathematical support operations for qcalc (numeric integration and statistics stuff). This isn't included in the package yet (sorry, Eddie, didn't have the time to look at it yet), so if you want this, please get in touch with him (he's on this list). NB, Eddie: I guess you're still running RC1 right now, if you have the time could you please check out R1_0_RC2 and tell me whether it still works with your spreadsheets? RC2 has a brandnew depth-first-search evaluation algorithm which also works with cyclic cell dependencies. NB, Rob: This isn't quite the Q+Q/Q[i][X] calculator program I promised a while ago, but it should be even better-suited for that purpose. :) But maybe it would be useful to work on ratutils.q and polynomial.q, in order to provide more "QCalc-friendly" frontends for some of the operations of these modules? If you're interested, please get in touch or post to the ml. Enjoy! :) Albert -- Dr. Albert Gr"af Dept. of Music-Informatics, University of Mainz, Germany Email: Dr....@t-..., ag...@mu... WWW: http://www.musikinformatik.uni-mainz.de/ag |
|
From: Albert G. <Dr....@t-...> - 2007-11-10 10:50:20
|
Hi all, well, I have been a bit silent (beginning of the winter semester over here), but not lazy, so here are some quick updates on the latest stuff: - Qt/Q 1.2 has been released. This is a bugfix release, upgrading is *strongly* recommended. Please note that this version also needs the latest Q from cvs and the latest Q-SWIG package (1.3.22-q-20071021). - I have also uploaded new RPMs (q-7.8-6) for the all-in-one package which contain the latest Qt/Q as well as all recent bugfixes to the Q 7.8 core package from cvs. (Note that the Q 7.8 tarball is still the "official" release, so you need to get the cvs sources if you're compiling Q from source, or you can extract the modified source tarball contained in the q-7.8-6 source rpm. I'll do an official bugfix release of the core package asap.) The new releases are now also available via the Download page at: http://q-lang.sourceforge.net/download.html Also, there's some additional new stuff in cvs, but I'll announce that separately, so stay tuned... Cheers, Albert -- Dr. Albert Gr"af Dept. of Music-Informatics, University of Mainz, Germany Email: Dr....@t-..., ag...@mu... WWW: http://www.musikinformatik.uni-mainz.de/ag |
|
From: Borse, G. <gan...@cr...> - 2007-10-31 06:53:59
|
Hi, Thanks for providing such great utility to convert rpm to targz. But, it depends on another tool rpmoffset, which is not available on our Linux system. Where can I get the same? Will that be an RPM? Please help. Thanks and Regards Ganesh ------------------------- Message: 2 Date: Tue, 23 Oct 2007 23:44:02 -0600 From: kruhft <kr...@gm...> Subject: Re: [q-lang-users] Request to know about using Q in C++ programs To: "Discuss the Q language." <q-l...@li...> Message-ID: <ace...@ma...> Content-Type: text/plain; charset=ISO-8859-1 On 10/23/07, Borse, Ganesh <gan...@cr...> wrote: You can always try rpm2targz: http://www.fship.com/demos/rpm2targz -- burton samograd http://metashell.org kr...@gm... ------------------------------------------------------------------------- ============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ============================================================================== |
|
From: Borse, G. <gan...@cr...> - 2007-10-30 04:10:32
|
Hi, Thanks for providing such great utility to convert rpm to targz. But, it depends on another tool rpmoffset, which is not available on our Linux system. Where can I get the same? Will that be an RPM? Please help. Thanks and Regards Ganesh ------------------------- Message: 2 Date: Tue, 23 Oct 2007 23:44:02 -0600 From: kruhft <kr...@gm...> Subject: Re: [q-lang-users] Request to know about using Q in C++ programs To: "Discuss the Q language." <q-l...@li...> Message-ID: <ace...@ma...> Content-Type: text/plain; charset=ISO-8859-1 On 10/23/07, Borse, Ganesh <gan...@cr...> wrote: You can always try rpm2targz: http://www.fship.com/demos/rpm2targz -- burton samograd http://metashell.org kr...@gm... ------------------------------------------------------------------------- ============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ============================================================================== |
|
From: Albert G. <Dr....@t-...> - 2007-10-27 19:59:15
|
Hi all, Gerard Milmeister, who thankfully maintains the Q package for Fedora, has reported an issue with Q 7.8 which causes a buffer overflow when you run q --help. That doesn't seem to have any disastrous consequences (q --help works in spite of it), but of course it had to be fixed, and I already did so in cvs. Thanks to Gerard for his bug report, and kudos for maintaining the Fedora Q packages. I've attached the necessary patch against Q 7.8, for those who prefer to work with tarballs. Also attached: a minor fix to the symbol table code, which makes extern redeclarations of virtual constructors possible (also in cvs). I will hopefully get around uploading a bugfix release for the core package before Xmas, but for the time being please apply those patches to your source, or use the cvs version. Thanks, Albert -- Dr. Albert Gr"af Dept. of Music-Informatics, University of Mainz, Germany Email: Dr....@t-..., ag...@mu... WWW: http://www.musikinformatik.uni-mainz.de/ag |
|
From: Albert G. <Dr....@t-...> - 2007-10-26 11:15:44
|
This has been answered already, why is this message being posted for the third time now? Borse, Ganesh wrote: > I would like to embed the Q interpreter in C++ application using the > libqint library. > [snipped] -- Dr. Albert Gr"af Dept. of Music-Informatics, University of Mainz, Germany Email: Dr....@t-..., ag...@mu... WWW: http://www.musikinformatik.uni-mainz.de/ag |
|
From: Borse, G. <gan...@cr...> - 2007-10-26 03:48:01
|
> Hi, > > I would like to embed the Q interpreter in C++ application using the libqint library. > > Is it sufficient to use only the "libqint" library for this? Or do I need to get all dependencies to link this library & use at run time with my program? > Other problem is that, I am not able to install RPMs "q-7.8-5su101.i586.rpm" & "q-7.8-5.src.rpm" on my Linux OS because I do NOT have root privileges. > While installing SRC RPM I got an error: error: cannot create %sourcedir /usr/src/redhat/SOURCES > I have only Red Hat Linux 3 (Taroon Updt1) & no SUSE. Can I have binaries for Red Hat Linux also in tar.gz format? > > Please guide/ help. > > Thanks, > Ganesh ============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ============================================================================== |
|
From: Borse, G. <gan...@cr...> - 2007-10-25 02:15:05
|
Hi, I would like to embed the Q interpreter in C++ application using the libqint library. Is it sufficient to use only the "libqint" library for this? Or do I need to get all dependencies to link this library & use at run time with my program? Other problem is that, I am not able to install RPMs "q-7.8-5su101.i586.rpm" & "q-7.8-5.src.rpm" on my Linux OS because I do NOT have root privileges. While installing SRC RPM I got an error: error: cannot create %sourcedir /usr/src/redhat/SOURCES I have only Red Hat Linux 3 (Taroon Updt1) & no SUSE. Can I have binaries for Red Hat Linux also in tar.gz format? Please guide/ help. Thanks, Ganesh ============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ============================================================================== |
|
From: Albert G. <Dr....@t-...> - 2007-10-24 15:21:30
|
John Cowan wrote: > I recommend building from source in that case. It's very easy: Right. Just remember to also set your path to the bin directory. Of course, if you build from the source, you also need some development packages (GNU C library and libgmp should be all that is needed for a basic install) on your system. Also check Fedora (the community-based RedHat version). Since FC6 they have a Q RPM package, too, maybe you can convince your sysadmin to install that on your machine. (It's an older Q version, though.) Albert -- Dr. Albert Gr"af Dept. of Music-Informatics, University of Mainz, Germany Email: Dr....@t-..., ag...@mu... WWW: http://www.musikinformatik.uni-mainz.de/ag |
|
From: John C. <co...@cc...> - 2007-10-24 12:37:17
|
Borse, Ganesh scripsit: > Since, I want to embed the Q interpreter in my C++ application, is it > sufficient to use only the "libqint" library for this? Or do I need > to get all dependencies to link this library & use at run time with > my program? The Linux linker is smart enough to pull in all the dependencies, usually, but for the record they are -lq and -lgmp. On other operating systems YMMV; Cygwin requires explicit -lq -lgmp -liconv. > Other problem is that, I am not able to install RPMs > "q-7.8-5su101.i586.rpm" & "q-7.8-5.src.rpm" on my Linux OS because I > do NOT have root privileges. While installing SRC RPM I got an error: > error: cannot create %sourcedir /usr/src/redhat/SOURCES I have only > Red Hat Linux 3 (Taroon Updt1) & no SUSE. Can I have binaries for Red > Hat Linux also in tar.gz format? I recommend building from source in that case. It's very easy: * unpack the tarball $ ./configure --prefix=some/directory $ make $ make install -- John Cowan co...@cc... At times of peril or dubitation, http://www.ccil.org/~cowan Perform swift circular ambulation, With loud and high-pitched ululation. |
|
From: kruhft <kr...@gm...> - 2007-10-24 05:44:06
|
On 10/23/07, Borse, Ganesh <gan...@cr...> wrote: > While installing SRC RPM I got an error: error: cannot create %sourcedir > /usr/src/redhat/SOURCES > I have only Red Hat Linux 3 (Taroon Updt1) & no SUSE. Can I have binaries > for Red Hat Linux also in tar.gz format? You can always try rpm2targz: http://www.fship.com/demos/rpm2targz -- burton samograd http://metashell.org kr...@gm... |
|
From: Borse, G. <gan...@cr...> - 2007-10-24 03:21:19
|
Hi, Thanks for your guidance. It is great this does not create a new process for interpreter. Since, I want to embed the Q interpreter in my C++ application, is it sufficient to use only the "libqint" library for this? Or do I need to get all dependencies to link this library & use at run time with my program? Other problem is that, I am not able to install RPMs "q-7.8-5su101.i586.rpm" & "q-7.8-5.src.rpm" on my Linux OS because I do NOT have root privileges. While installing SRC RPM I got an error: error: cannot create %sourcedir /usr/src/redhat/SOURCES I have only Red Hat Linux 3 (Taroon Updt1) & no SUSE. Can I have binaries for Red Hat Linux also in tar.gz format? Please guide/ help. Many thanks for your time & guidance. Warm Regards Ganesh ------------------------------------------------------------------------------------------------------------- Message: 8 Date: Tue, 23 Oct 2007 10:38:02 -0400 From: John Cowan <co...@cc...> Subject: Re: [q-lang-users] Request to know about using Q in C++ programs To: "Discuss the Q language." <q-l...@li...> Message-ID: <200...@me...> Content-Type: text/plain; charset=us-ascii Borse, Ganesh scripsit: > In the topic "C.4 Embedding Q in C/C++ Applications " on web page "http://q-lang.sourceforge.net/qdoc/qdoc_15.html#SEC187 <http://q-lang.sourceforge.net/qdoc/qdoc_15.html#SEC187> <http://q-lang.sourceforge.net/qdoc/qdoc_15.html#SEC187 <http://q-lang.sourceforge.net/qdoc/qdoc_15.html#SEC187> > ", it mentioned > that before calling any eval functions from Q library, we need to do qexecv() or qexecl(). > > Does this mean that we create / fork a process from the parent C/ C++ program & then the script gets loaded into that new process? Not at all. qexecv() and qexecl() cause the Q interpreter to load a script to be run by the interpreter in the current process. They do not cause an underlying execv() or execl(), but are only generally analogous to them (start new script, pass arguments). -- Even the best of friends cannot John Cowan attend each others' funeral. co...@cc... --Kehlog Albran, The Profit http://www.ccil.org/~cowan <http://www.ccil.org/~cowan> > _____________________________________________ > From: Borse, Ganesh > Sent: 23 October 2007 20:42 > To: 'q-l...@li...' > Subject: Request to know about using Q in C++ programs > > Dear Sir, > I am impressed with the great feature of dynamic expression evaluation provided by Q language. > > I would like to use this for a C++ application which takes dynamic expressions like queries from database > > However, I want to do this in the same process & not over the other process. > > In the topic "C.4 Embedding Q in C/C++ Applications " on web page "http://q-lang.sourceforge.net/qdoc/qdoc_15.html#SEC187 <http://q-lang.sourceforge.net/qdoc/qdoc_15.html#SEC187> ", it mentioned that before calling any eval functions from Q library, we need to do qexecv() or qexecl(). > > Does this mean that we create / fork a process from the parent C/ C++ program & then the script gets loaded into that new process? > Please advise. > > Many thanks for your help. > > Warm Regards, > Ganesh ============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ============================================================================== |
|
From: John C. <co...@cc...> - 2007-10-23 14:38:26
|
Borse, Ganesh scripsit: > In the topic "C.4 Embedding Q in C/C++ Applications " on web > page "http://q-lang.sourceforge.net/qdoc/qdoc_15.html#SEC187 > <http://q-lang.sourceforge.net/qdoc/qdoc_15.html#SEC187> ", it mentioned > that before calling any eval functions from Q library, we need to do > qexecv() or qexecl(). > > Does this mean that we create / fork a process from the parent C/ C++ > program & then the script gets loaded into that new process? Not at all. qexecv() and qexecl() cause the Q interpreter to load a script to be run by the interpreter in the current process. They do not cause an underlying execv() or execl(), but are only generally analogous to them (start new script, pass arguments). -- Even the best of friends cannot John Cowan attend each others' funeral. co...@cc... --Kehlog Albran, The Profit http://www.ccil.org/~cowan |
|
From: Borse, G. <gan...@cr...> - 2007-10-23 12:42:44
|
Dear Sir, I am impressed with the great feature of dynamic expression evaluation provided by Q language. I would like to use this for a C++ application which takes dynamic expressions like queries from database However, I want to do this in the same process & not over the other process. In the topic "C.4 Embedding Q in C/C++ Applications " on web page "http://q-lang.sourceforge.net/qdoc/qdoc_15.html#SEC187 <http://q-lang.sourceforge.net/qdoc/qdoc_15.html#SEC187> ", it mentioned that before calling any eval functions from Q library, we need to do qexecv() or qexecl(). Does this mean that we create / fork a process from the parent C/ C++ program & then the script gets loaded into that new process? Please advise. Many thanks for your help. Warm Regards, Ganesh ============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ============================================================================== |
|
From: Albert G. <Dr....@t-...> - 2007-10-21 04:05:50
|
A new Q-SWIG version (1.3.22-q-20071021) is now available, too. It fixes some minor bugs (already reported by Andrew Berg and others ages ago) and adds support for %virtual declarations, so that virtual constructors can be implemented as extern C/C++ functions. Albert -- Dr. Albert Gr"af Dept. of Music-Informatics, University of Mainz, Germany Email: Dr....@t-..., ag...@mu... WWW: http://www.musikinformatik.uni-mainz.de/ag |
|
From: Albert G. <Dr....@t-...> - 2007-10-20 13:17:26
|
Update: - Windows: The msi lacked the new reftypes.q module, so I've uploaded a new package. - Zaurus: The OpenZaurus feed now has Q 7.8 as well. While I was at it, I also noticed and fixed a few minor glitches in the reference vector examples in chapter 12 of the manual, and uploaded new RPMs and tarball. (No need to upgrade if you're not bothered by a few silly typos.) Cheers, Albert -- Dr. Albert Gr"af Dept. of Music-Informatics, University of Mainz, Germany Email: Dr....@t-..., ag...@mu... WWW: http://www.musikinformatik.uni-mainz.de/ag |
|
From: Albert G. <Dr....@t-...> - 2007-10-18 20:32:28
|
Dear all, some of you already noticed it, as I have been uploading stuff since yesterday, so this announcement comes a bit late. ;-) Meanwhile, I have also updated the website, so you can now grab the new stuff from the Download page as well: http://q-lang.sourceforge.net/download.html The new release is more or less the same as 7.8RC2, but with some additional bugfixes and Qt/Q examples. In particular, if you installed the RPM, you might want to try a nice game of pong (qpong), which I included as a little bonus. :) If you are installing from sources instead, you can find the game in a separate source package, qpong-1.0.tar.gz, available in the "grab bag" on the Examples page. Those of you who already got the 7.8-3 RPM yesterday should consider to get the latest one uploaded last night (7.8-4). I still found a little bug in the qmidicc application and already fixed it. I know that the Windows users among you will be disappointed that the Qt/Q module isn't included in the Windows package yet, I'm still working on this and didn't want to withhold the release any longer. But all the new stuff should soon be available on Windows as well. I'll post an announcement here as soon as I release an updated Windows package. Ok, so please enjoy the latest and greatest Q release. :) Cheers, Albert -- Dr. Albert Gr"af Dept. of Music-Informatics, University of Mainz, Germany Email: Dr....@t-..., ag...@mu... WWW: http://www.musikinformatik.uni-mainz.de/ag |
|
From: <ed...@ri...> - 2007-10-15 14:24:33
|
=0D Eddie Rucker wrote:=0D > > Hope you are having a good vacation :) In the meantime, I forgot what= we =0D > > wanted for the appendix for qdoc. Since you already have the stdlib and= =0D > > clib should this include:=0D =0D Hmm, I thought you just wanted to do an xref for the stuff that's=0D already there? Anyway, all the modules (core or addon) you mention=0D aren't documented in the manual yet, so clearly covering these in the=0D manual would be useful. But doing full documentation for all of these is=0D a herculean task.=0D =0D For the beginning, it would be nice to have just a listing of the=0D available functions, with module names and maybe line numbers of=0D definitions, and a reference to the manual where applicable. Of course=0D this information would be most useful if it also included the core and=0D addon modules. Most of this information should be easily obtainable=0D using a script invoking completion_matches, whois and a search of the=0D manual index. The script could then be used to regenerate the crossref=0D whenever some part of the library changes so that it would always be=0D up-to-date.=0D =0D > > Curl=0D > > GNU dbm=0D > > ODBC=0D > > Octave=0D > > GGI=0D > > ImageMagick=0D > > Tcl/Tk=0D > > IBM's Data Explorer=0D > > =0D > > and should the appendix be titled "Module Reference."=0D > > =0D > > Or was it suppose to include all of the add-ons:=0D > > =0D > > Qt-Q,=0D > > Qmidi,=0D > > etc, ...=0D =0D > > I've gotten some things done on the Xref for which I would like to =0D > > include all of the functions for modules and add-ons. I'm thinking I = =0D > > should stop and concentrate my effort on the Appendix first. What do yo= u =0D > > think?=0D =0D Again, I thought that we were talking about the xref, to make that an=0D appendix of the manual? But of course any other material for the manual=0D is welcome, too!=0D =0D Albert=0D =0D -- Dr. Albert Gr"af Dept. of Music-Informatics, University of Mainz, German= y=0D Email: Dr....@t-..., ag...@mu... WWW:=0D http://www.musikinformatik.uni-mainz.de/ag=0D ------------------------------------------------------------------------- T= his=0D SF.net email is sponsored by: Splunk Inc. Still grepping through log files = to=0D find problems? Stop. Now Search log events and configuration files using AJ= AX and=0D a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/= =0D _______________________________________________ q-lang-users mailing list= =0D q-l...@li...=0D https://lists.sourceforge.net/lists/listinfo/q-lang-users =0D |
|
From: <ed...@ri...> - 2007-10-15 14:23:11
|
=0D Albert:=0D =0D Hope you are having a good vacation :) In the meantime, I forgot what we wa= nted=0D for the appendix for qdoc. Since you already have the stdlib and clib shoul= d this=0D include:=0D =0D Curl=0D GNU dbm=0D ODBC=0D Octave=0D GGI=0D ImageMagick=0D Tcl/Tk=0D IBM's Data Explorer=0D =0D and should the appendix be titled "Module Reference."=0D =0D Or was it suppose to include all of the add-ons:=0D =0D Qt-Q,=0D Qmidi,=0D etc, ...=0D =0D I've gotten some things done on the Xref for which I would like to include = all of=0D the functions for modules and add-ons. I'm thinking I should stop and conce= ntrate=0D my effort on the Appendix first. What do you think?=0D =0D Eddie =0D =0D |
|
From: Albert G. <Dr....@t-...> - 2007-10-14 22:51:10
|
Eddie Rucker wrote: > Hope you are having a good vacation :) In the meantime, I forgot what we > wanted for the appendix for qdoc. Since you already have the stdlib and > clib should this include: Hmm, I thought you just wanted to do an xref for the stuff that's already there? Anyway, all the modules (core or addon) you mention aren't documented in the manual yet, so clearly covering these in the manual would be useful. But doing full documentation for all of these is a herculean task. For the beginning, it would be nice to have just a listing of the available functions, with module names and maybe line numbers of definitions, and a reference to the manual where applicable. Of course this information would be most useful if it also included the core and addon modules. Most of this information should be easily obtainable using a script invoking completion_matches, whois and a search of the manual index. The script could then be used to regenerate the crossref whenever some part of the library changes so that it would always be up-to-date. > Curl > GNU dbm > ODBC > Octave > GGI > ImageMagick > Tcl/Tk > IBM's Data Explorer > > and should the appendix be titled "Module Reference." > > Or was it suppose to include all of the add-ons: > > Qt-Q, > Qmidi, > etc, ... > I've gotten some things done on the Xref for which I would like to > include all of the functions for modules and add-ons. I'm thinking I > should stop and concentrate my effort on the Appendix first. What do you > think? Again, I thought that we were talking about the xref, to make that an appendix of the manual? But of course any other material for the manual is welcome, too! Albert -- Dr. Albert Gr"af Dept. of Music-Informatics, University of Mainz, Germany Email: Dr....@t-..., ag...@mu... WWW: http://www.musikinformatik.uni-mainz.de/ag |
|
From: Albert G. <Dr....@t-...> - 2007-10-14 21:02:49
|
Eddie Rucker wrote: > Note: To get qt-q going on Debian, you'll need a train-load of stuff: Thanks for the information, that should be helpful for Debian users. BTW, does your list of packages also include SmokeQt? Or did you install that from source? Is there a package in Debian which contains SmokeQt? > I wonder if this is going to > make portable q/qt scripts across Linux, MAC, and Windoze difficult? I don't think so. Besides SmokeQt, Qt/Q only uses standard Qt stuff (libqt, libqui, libqassistantclient) which should be available on any platform supported by Qt. The distro-specific packaging of Qt may make it a little harder to compile Qt/Q on some systems, but once it is up and running, existing Qt/Q scripts should just work. Maybe some kind soul will eventually take care of doing an "all-in-one" Q package for Debian which includes Qt/Q. It shouldn't be too hard to do this, as the complete build process for all things Q on Unix-like systems is already documented in the RPM spec file. I always wanted to have a look at Debian myself, but unfortunately I'm just too busy with other things right now. Albert -- Dr. Albert Gr"af Dept. of Music-Informatics, University of Mainz, Germany Email: Dr....@t-..., ag...@mu... WWW: http://www.musikinformatik.uni-mainz.de/ag |
|
From: Eddie R. <ed...@ri...> - 2007-10-11 20:18:49
|
Albert: Hope you are having a good vacation :) In the meantime, I forgot what we wanted for the appendix for qdoc. Since you already have the stdlib and clib should this include: Curl GNU dbm ODBC Octave GGI ImageMagick Tcl/Tk IBM's Data Explorer and should the appendix be titled "Module Reference." Or was it suppose to include all of the add-ons: Qt-Q, Qmidi, etc, ... I've gotten some things done on the Xref for which I would like to include all of the functions for modules and add-ons. I'm thinking I should stop and concentrate my effort on the Appendix first. What do you think? Eddie |
|
From: Eddie R. <ed...@ri...> - 2007-10-08 16:28:02
|
Note: To get qt-q going on Debian, you'll need a train-load of stuff: libqt3-headers libqt3-mt-dev qt3-assistant qt3-apps-dev qt3-dev-tools If you use apt-get, it will automatically include a train-load more stuff under each to satisfy dependencies. I wonder if this is going to make portable q/qt scripts across Linux, MAC, and Windoze difficult? Eddie Albert Graef wrote: > I've just uploaded the latest RPMs for RC2, which now also include the > latest faust2pd script and some minor fixes in qfsynth. > |
38 messages has been excluded from this view by a project administrator.
