Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Direction for C# Sqlite.
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Miguel de Icaza  
View profile  
 More options Aug 9 2009, 12:44 pm
From: Miguel de Icaza <miguel.de.ic...@gmail.com>
Date: Sun, 9 Aug 2009 09:44:25 -0700 (PDT)
Local: Sun, Aug 9 2009 12:44 pm
Subject: Direction for C# Sqlite.
Hello,

    Noah, I am wondering where you would like to take the project from
here.   It is a fantastic thing to have Sqlite ported to C#.   The
current downside is that it is very much a one-to-one mapping to C and
it does not take advantage of C# features available to it.

     I would personally want to C#-ify the code, and I am wondering
how do you feel about that?

Some things that could be done:

* Replace manual memory management (strlen30, free, sqlite_sprintf and
others with the C# equivalents where possible).

* Avoid using the emulated C library functions and instead use
the .NET ones (for example there are many of those on src/shell.cs at
the bottom).

* Avoid using printf, but use Console.WriteLine instead.

* Use the "using" construct for automatically disposing objects.

* Avoid depending on #ifdef WIN32 for example to produce libraries
that are OS specific, and instead make those runtime detectable
features.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.