Miguel de Icaza wrote:
* Is this the fix for delegates?
* Is this the fix for the ref/out you talked about before?
Okay, now we have those. Updating all of the ECMA docs took a while to
make sure no information was being lost as I ran all of the xml files
through a stylesheet.
Very little mention is ever made of qt#. The website has quite a bit of
info on gtk#, but 0 mention of Qt#. Is this a throwback to the GNOME vs
KDE arguments? Just an oversight? What gives?
dan
--
Life is short. Play naked.
wrevolution.org
signature.asc
Description: This is a digitally
Hi all,
it's a great pleasure to say Npgsql has a new release!
From Release Notes:
Npgsql 0.5 development release.
What's new in this version:
- New datatypes supported: bool, int2, int4, int8, numeric, timestamp,
date, time and text data types.
These types are mapped to DbTtype enum: Boolean,
Francisco Figueiredo Jr. wrote:
Ooops, I forgot to say this:
Npgsql is a .net data provider for Postgresql. It works on both Mono and
MS runtime.
You can download it from here:
http://gborg.postgresql.org/project/npgsql
You can also find info about it in the following site:
To run with Mono, download the archive, rename XPathDocument.cs.txt
to XPathDocument.cs and replace existing XPathDocument with it, and
copy the others to anyplace to be compiled (e.g. System.Xml.XPath).
I forgot to say that you have to add those new files to list.unix
to build them ;)
I've been trying to run a simple program on mono that sends a Udp
datagram I can't make it work. I don't know if I have done something
wrong or maybe there is some bug on mono?
Thanks in advance.
using System;
using System.Net;
using System.Net.Sockets;
class client {
static UdpClient
Steve Homer wrote:
Hi all,
I've been attempting to build mono cvs (as of 02:00 GMT+1) on Redhat 9
via the given script (mono-build.sh). It fails someway through the build
with a bunch of errors relating to not being able to stat what looks
like a set of assemblies.
Yes, this is normal, as you
On 06/01/03 Dan Trevino wrote:
Very little mention is ever made of qt#. The website has quite a bit of
info on gtk#, but 0 mention of Qt#. Is this a throwback to the GNOME vs
KDE arguments? Just an oversight? What gives?
It gives that no one of the Qt# users bothered to post a patch to add
I think this is the serious omission. So, it seems that Qt as a
part of KDE is very popular in the Europe as well as in Russia.
It would be just fine to have the fully-functional Qt# but not
only gtk#.
By the way, is it possible possible to design something common,
which can be implemented
On 06/02/03 David Sorokin wrote:
I think this is the serious omission. So, it seems that Qt as a
Fine, what about if you do something about it instead of whining on
the list?
It would be just fine to have the fully-functional Qt# but not
only gtk#.
I couldn't find a single bug report from
10 matches
Mail list logo
