From: Brian O. <br...@qi...> - 2003-08-03 21:13:50
|
> The problem of implementing user-defined types using Python is that, > to my > knowledge, Python is one of the languages that belong to the 'object > world', which is, sadly, incompatible with D in many respects. > > These languages, for example, are heavily using references, which are > not > allowed in a Database in D. This has important consequences for > user-defined types. Yeah, I see what you mean here. That didn't occur to me. > For example, read the discussion about the difference between D > selectors and object world constructors at the end of the informal > discussion of RM prescripion 4 in chapter 6 of the TTM. > You must be aware of these problems if you try to implement D using an > OO > language like Python. Figuring the disparity between approaches, I was figuring that something would pop up. :-( Described in RM Prescription 4, this situation certainly complicates this issue a lot. > Well, I am not sure what would be gained by starting to implement a D > system in Python using Berkeley DB, because that would very much repeat > the work which was already done (or will be done) to implement Duro. I > don't think the possibility to use the Berkeley DB Python API > compensates > for this. > > As Leandro suggested, it may be a better idea to write a Python > interface > for Duro. This would have to be done in C, but would be much less work. This could just be the best approach then. I'd rather learn than compete. :-) Thanks. Brian |