q-lang-users

[q-lang-users] Q in FC6

[Albert G. <Dr....@t-...>]

Hi all,

The RedHat users among you might be interested in this. I just noticed
that Q is now in the Fedore extras tree, see
http://fedoraproject.org/extras/6/i386/repodata/repoview/q-0-7.5-1.fc6.html

Nice to see that some distributions are finally picking it up. Makes my
task a little easier. ;-)

Cheers,
Albert

P.S.: If anyone here has tried the FC Q packages, I'd be interested to
hear whether they are actually working, what stuff is missing, etc.

-- 
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

Re: [q-lang-users] Q in FC6

[Burton S. <kr...@gm...>]

I'm working on getting ebuild's written for Gentoo, almost as we
speak.  I have the core interpreter installation working that handles
USE flags properly (AFAIK), and I'll be working on the add on modules
as I find time.

On 11/23/06, Albert Graef <Dr....@t-...> wrote:
> Hi all,
>
> The RedHat users among you might be interested in this. I just noticed
> that Q is now in the Fedore extras tree, see
> http://fedoraproject.org/extras/6/i386/repodata/repoview/q-0-7.5-1.fc6.html
>
> Nice to see that some distributions are finally picking it up. Makes my
> task a little easier. ;-)
>
> Cheers,
> Albert
>
> P.S.: If anyone here has tried the FC Q packages, I'd be interested to
> hear whether they are actually working, what stuff is missing, etc.
>
> --
> 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
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> q-lang-users mailing list
> q-l...@li...
> https://lists.sourceforge.net/lists/listinfo/q-lang-users
>


-- 
burton samograd                                                kr...@gm...
kruhft.boldlygoingnowhere.org              www.myspace.com/kruhft

Re: [q-lang-users] Q in FC6

[Albert G. <Dr....@t-...>]

Burton Samograd wrote:
> I'm working on getting ebuild's written for Gentoo, almost as we
> speak.  I have the core interpreter installation working that handles
> USE flags properly (AFAIK), and I'll be working on the add on modules
> as I find time.

Hi Burton,

that's very good news! Thanks a lot for your work on this. Please let me
know if you run into any portability quirks so that I can add the
necessary patches to the next release.

Now, is there anyone out there who might be willing to maintain a Debian
package? Kari Pahula was working on this quite a while ago, but I can't
find his package on mentor.debian.net any more.

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

Re: [q-lang-users] Q in FC6

[Burton S. <kr...@gm...>]

Hi Albert,

> Burton Samograd wrote:
> > I'm working on getting ebuild's written for Gentoo, almost as we
> > speak.  I have the core interpreter installation working that handles
> > USE flags properly (AFAIK), and I'll be working on the add on modules
> > as I find time.

I submitted my Q-7.5 ebuild to gentoo.  Those who wish to try it can
find it here:

http://bugs.gentoo.org/show_bug.cgi?id=156102

I tested it and it works fine on my system and since it mostly
autoconfigures itself when packages are present, the ebuild just
disables features if certain USE flags aren't set. Hopefully I managed
to get everything right with all of them.

> that's very good news! Thanks a lot for your work on this. Please let me
> know if you run into any portability quirks so that I can add the
> necessary patches to the next release.

No problems at all with compiling on my system.

-- 
burton samograd                                                kr...@gm...
kruhft.boldlygoingnowhere.org              www.myspace.com/kruhft

Re: [q-lang-users] Q in FC6

[Tim H. <q...@st...>]

"Burton Samograd" <kr...@gm...> writes:

> Hi Albert,
> 
> > Burton Samograd wrote:
> > > I'm working on getting ebuild's written for Gentoo, almost as we
> > > speak.  I have the core interpreter installation working that handles
> > > USE flags properly (AFAIK), and I'll be working on the add on modules
> > > as I find time.
> 
> I submitted my Q-7.5 ebuild to gentoo.  Those who wish to try it can
> find it here:
> 
> http://bugs.gentoo.org/show_bug.cgi?id=156102
> 
> I tested it and it works fine on my system and since it mostly
> autoconfigures itself when packages are present, the ebuild just
> disables features if certain USE flags aren't set. Hopefully I managed
> to get everything right with all of them.

OK, I've got it installed and basically functional here on an athlon-xp box:

[ebuild  N    ] dev-lang/q-7.5  USE="curl gdbm gmp iconv imagemagick odbc readline threads unicode xml -X -dmalloc -freetype -ggi -nls -tk -virtual/libc" 0 kB [1]

I note 3 things:
a) isn't GMP more a requirement for Q than an optional USE thing?

b) interestingly, you've got the odbc option but it rebuilt libiodbc as a
dependency before building Q. Not that I'm complaining[1], of course.

c) A minor (probably only visual) niggle. This strikes me as having a few
too many commas for my sanity:

 | ==> import odbc
 | 
 | ==> def H=odbc_connect "DSN=pgstraw"
 | 
 | ==> sql H "select count(*) from gallery" ()
 | [("count",),(1770,)]
 
I have both unixODBC and iODBC installed; on this box, Q's odbc.so is
linked against unixODBC; neither iodbctest nor isql hint at a second
column; versions of Q >=6.2incl exhibit this spare comma. I note I can type
[1,2,3,] into the interpreter and get back [1,2,3] for my trouble (so I'd
expect the above resultset display to be normalized too). Am I missing some
update somewhere?


[1] <cough> I'm also webmaster for iodbc </cough>

~Tim
-- 
<http://spodzone.org.uk/>

Re: [q-lang-users] Q in FC6

[Burton S. <kr...@gm...>]

Hi Tim,

Thanks for testing the ebuild. See comments below.

On 24 Nov 2006 14:54:34 +0000, Tim Haynes <q...@st...> wrote:
> a) isn't GMP more a requirement for Q than an optional USE thing?

Correct.  My mistake; I removed gmp from the configuration section,
added gmp as a real dependancy.

> b) interestingly, you've got the odbc option but it rebuilt libiodbc as a
> dependency before building Q. Not that I'm complaining[1], of course.

I looked at the Q docs and found that it supported libiodbc and
UNIXodbc; I just picked one, since I don't use the ODBC functionality
at all.

> c) A minor (probably only visual) niggle. This strikes me as having a few
> too many commas for my sanity:
>
>  | ==> import odbc
>  |
>  | ==> def H=odbc_connect "DSN=pgstraw"
>  |
>  | ==> sql H "select count(*) from gallery" ()
>  | [("count",),(1770,)]
>
> I have both unixODBC and iODBC installed; on this box, Q's odbc.so is
> linked against unixODBC; neither iodbctest nor isql hint at a second
> column; versions of Q >=6.2incl exhibit this spare comma. I note I can type
> [1,2,3,] into the interpreter and get back [1,2,3] for my trouble (so I'd
> expect the above resultset display to be normalized too). Am I missing some
> update somewhere?

Not sure about this problem since I don't use the ODBC at all.  Maybe
I should default to using the unixODBC instead?  How about I do that
and you test it and tell me if that works better for you and I'll
leave it.

I'll have the new ebuild up in a couple of minutes.

-- 
burton samograd                                                kr...@gm...
kruhft.boldlygoingnowhere.org              www.myspace.com/kruhft

Re: [q-lang-users] Q in FC6

[Tim H. <q...@st...>]

"Burton Samograd" <kr...@gm...> writes:

[snip]
> I looked at the Q docs and found that it supported libiodbc and
> UNIXodbc; I just picked one, since I don't use the ODBC functionality
> at all.

You could make both odbc and iodbc into optional USE flags.

Albert: it would be nice if ./configure understood --with-iodbc and then
went on to use `iodbc-config --cflags` and --libs.

> > c) A minor (probably only visual) niggle. This strikes me as having a few
> > too many commas for my sanity:
> >
> >  | ==> import odbc
> >  |
> >  | ==> def H=odbc_connect "DSN=pgstraw"
> >  |
> >  | ==> sql H "select count(*) from gallery" ()
> >  | [("count",),(1770,)]
> >
> > I have both unixODBC and iODBC installed; on this box, Q's odbc.so is
> > linked against unixODBC; neither iodbctest nor isql hint at a second
> > column; versions of Q >=6.2incl exhibit this spare comma. I note I can type
> > [1,2,3,] into the interpreter and get back [1,2,3] for my trouble (so I'd
> > expect the above resultset display to be normalized too). Am I missing some
> > update somewhere?
> 
> Not sure about this problem since I don't use the ODBC at all. Maybe I
> should default to using the unixODBC instead? How about I do that and you
> test it and tell me if that works better for you and I'll leave it.
> 
> I'll have the new ebuild up in a couple of minutes.

Further testing has eliminated the role of driver manager here; it's just
down to Q how the extra comma is coming into play.

~Tim
-- 
<http://spodzone.org.uk/>

Re: [q-lang-users] Q in FC6

[Burton S. <kr...@gm...>]

On 24 Nov 2006 15:59:26 +0000, Tim Haynes <q...@st...> wrote:
> "Burton Samograd" <kr...@gm...> writes:
>
> [snip]
> > I looked at the Q docs and found that it supported libiodbc and
> > UNIXodbc; I just picked one, since I don't use the ODBC functionality
> > at all.
>
> You could make both odbc and iodbc into optional USE flags.

Done.  The configuration section checks for both and if neither are
enabled odbc is disabled.

> Albert: it would be nice if ./configure understood --with-iodbc and then
> went on to use `iodbc-config --cflags` and --libs.

Yes, if it handled both independently then the ebuild might be a bit
nicer.  Right now it's up to whether either flag is set, and which
ever one configure finds first, I guess.

-- 
burton samograd                                                kr...@gm...
kruhft.boldlygoingnowhere.org              www.myspace.com/kruhft

Re: [q-lang-users] Q in FC6

[Albert G. <Dr....@t-...>]

Burton Samograd wrote:
>> Albert: it would be nice if ./configure understood --with-iodbc and then
>> went on to use `iodbc-config --cflags` and --libs.
> 
> Yes, if it handled both independently then the ebuild might be a bit
> nicer.  Right now it's up to whether either flag is set, and which
> ever one configure finds first, I guess.

You guys probably know much more about ODBC than me. ;-) There's already
a section for ODBC flags in configure.in, so if someone can massage that
into something which is nicer/easier to use I'll be glad to add that to
the next release.

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

Re: [q-lang-users] Q in FC6

[John C. <co...@cc...>]

Tim Haynes scripsit:

> c) A minor (probably only visual) niggle. This strikes me as having
> a few too many commas for my sanity:
> 
>  | ==> import odbc
>  | 
>  | ==> def H=odbc_connect "DSN=pgstraw"
>  | 
>  | ==> sql H "select count(*) from gallery" ()
>  | [("count",),(1770,)]
>  
> I have both unixODBC and iODBC installed; on this box, Q's odbc.so is
> linked against unixODBC; neither iodbctest nor isql hint at a second
> column; versions of Q >=6.2incl exhibit this spare comma. 

No.  That's the way that Q (>=6.2, as you say) represents a tuple
with one element.  The syntax used to be just "(1770)", but that meant
different things in different contexts: it meant a tuple if the parens
were redundant, or just a plain expression of the parens were necessary
because of operator priorities.

I successfully argued that this was obnoxious, and Q was changed to use
the same syntax as Python: the final element in a tuple MAY be followed
by a comma, and MUST be if it is the only element.  Naturally, the
unparser follows the same rule, inserting the final comma only in
singletons.

> I note I can type [1,2,3,] into the interpreter and get back [1,2,3]
> for my trouble (so I'd expect the above resultset display to be
> normalized too). Am I missing some update somewhere?

Lists can't be confused with simple parens, so the final comma is
never necessary and the unparser will not generate it.

-- 
Kill Gorgun!  Kill orc-folk!            John Cowan
No other words please Wild Men.         co...@cc...
Drive away bad air and darkness         http://www.ccil.org/~cowan
with bright iron!   --Ghan-buri-Ghan    http://www.ccil.org/~cowan

Re: [q-lang-users] Q in FC6

[Tim H. <q...@st...>]

John Cowan <co...@cc...> writes:

[snip]
> No. That's the way that Q (>=6.2, as you say) represents a tuple with one
> element. The syntax used to be just "(1770)", but that meant different
> things in different contexts: it meant a tuple if the parens were
> redundant, or just a plain expression of the parens were necessary
> because of operator priorities.
> 
> I successfully argued that this was obnoxious, and Q was changed to use
> the same syntax as Python: the final element in a tuple MAY be followed
> by a comma, and MUST be if it is the only element. Naturally, the
> unparser follows the same rule, inserting the final comma only in
> singletons.
[snip]
> Lists can't be confused with simple parens, so the final comma is
> never necessary and the unparser will not generate it.

Ah, cool. OK, that explains things. Thanks :)

~Tim
-- 
<http://spodzone.org.uk/>