search for: gimb

...ction( :adapter => ''sqlite3'', :database => ''database/camping.db'' ) Camping::FastCGI.serve(''blog.rb'') Without ScriptAlias the application works fine, but only if I give the url with "index.fcgi/" at the end (http://localhost/~gimb/camping/index.fcgi/). Loading http://localhost/~gimb/camping/ or http://localhost/~gimb/camping/index.fcgi (no slash at the end) gives an error: ./lib/camping/fastcgi.rb:180:in `camp_do'': undefined local variable or method `exc'' for #<Camping::FastCGI:0xb78443e4> (NameE...

Hello all, I'd like to know if there is any interest in a Samba with LDAP HOWTO using Samba 3.0? During the last days I was compiling some documentation about it and I would be prepared to write some documentation. I didn't do any detailed search on the 'net however I'm unaware of any comprehensive howto on this topic. Bostjan Golob Gimnazija Bezigrad NOC

Hello, everyone! My name is Žiga Osolin and I am one of administrators of baadengine project (www.baadengine.org). It is an open source, BSD-licenced, game engine. We are very interested in llvm to provide us runtime code generation (basically, wrappers to easily call scripts from C++ and vica-versa, via vtbl (we replace vtbl for scripted types)) and also to allow our VM to run on llvm. Our

Hi, everyone! I decided to make llvm port on windows, to support at least Visual Studio 7.1 and Visual Studio 8. I guess I will make only Visual Studio 7.1 version, since it can be easily converted to version 8. I am using the already made build system made by Morten Ofstad. I don't know how long has it been when he left, but most of the projects are there, only some files are missing and

I downloaded the prebuild mingw 1.9 release and tried to extract the archine with WinRAR (latest), but it didn't work, says that archive is currupt. The source release was extracted correctly ... Žiga

I was wondering if (and when) is the full C++ compiling support (as it was with llvm3) to be expected (this mainly means the addition of EH to llvm)? Regards, Žiga

Hello (again)! I fixed most of the system and the following projects compile now: * Analysis * AsmParser * Bytecode * CBeckend * Codegen * ExecutionEngine * Support * System * TableGen * Target * Transforms * VMCore I would like to compile at least x86 target as well as Fibonacci example (to test if it really works). In order to do so, I may need some hints: 1) How to generate

Chris Lattner pravi: > On Tue, 21 Nov 2006, [ISO-8859-2] Žiga Osolin wrote: >>> Sure. Anton can give you ideas for this. >>> >> I think it should not be too difficult because you allow custom call >> conversions and this is quite easy to add, we only have to garantee that >> the backend will emit it. > > Right. > >>>> 2) the ret

I was going through documentation and source lately, and I decided how to make llvm bytecode more compatible to C++: 1) thiscall sould be introduced, which would take N arguments and the first argument would always be the C++ "this" argument. This would abstract llvm compiler dependant C++ code emition. 2) the ret instruction should be able to return structs (as Chris has already

I made the windows port, the first example compiled and executed correctly. I am sending a patch so you can test it if i didn't break linux compatibility. Otherwise, I will look into deja-gnu testing, perhaps can compile it on windows. I will also add other beckend in the future (Sparc, PowerPC). I hope windows using Visual C++ will be soon officially supported :) About the problem I had

Hello! I have a question how about JIT-ed code and the C++ compiler compatibily. My project (www.baadengine.org) will use llvm and we will provide integration of JIT-ed code directly into C++ code. This means that C++ code can call JIT code just like any other code and JIT-ed code can call C++ code. We will compile to your bytecode from our BSF format. The question is if it is possible this

I was going through documentation and source lately, and I decided how to make llvm bytecode more compatible to C++: 1) thiscall sould be introduced, which would take N arguments and the first argument would always be the C++ "this" argument. This would abstract llvm compiler dependant C++ code emittion. 2) the ret instruction should be able to return structs (as Chris has already

Chris Lattner pravi: > On Tue, 21 Nov 2006, [ISO-8859-2] Žiga Osolin wrote: >> I was going through documentation and source lately, and I decided >> how to >> make llvm bytecode more compatible to C++: >> 1) thiscall sould be introduced, which would take N arguments and the >> first argument would always be the C++ "this" argument. This would >>

> On Mon, 6 Nov 2006, [ISO-8859-2] Žiga Osolin wrote: >> The other thing are the return types. I don't know (it is probably even >> not documented) how VC++ returns smart pointer (boost::smart_ptr), >> or any other type (other basics types, such as int, float, ... are >> probably returned into EAX as with GCC). Once again, we may >> need specific return values

Chris Lattner pravi: > On Sat, 18 Nov 2006, [ISO-8859-2] Žiga Osolin wrote: >> I am currently trying to make EH (exception handling) possible to be >> integrated in C++. This means that C++ code can throw exceptions and >> llvm code can catch such exception and llvm can throw exceptions that >> C++ can catch (or pass through). There are quite some difficulties with

Anton Korobeynikov pravi: > Hello, Ziga. > > >> VCPP throws a warning that class is previously declared as struct. >> Either it must be struct everywhere or class everywhere. >> Declaration uses struct, while the definition uses class. >> > Nice! However it will be better to do the opposite: have it struct > everywhere. I'll fix this. >

Hello! I am currently trying to make EH (exception handling) possible to be integrated in C++. This means that C++ code can throw exceptions and llvm code can catch such exception and llvm can throw exceptions that C++ can catch (or pass through). There are quite some difficulties with approach: * I must write ABI specific backends for EH. Since we support Visual Studio and GCC, two