12.03.2014 14:48, Alex Peshkoff wrote: > For different versions we need to take into an account differetnt > offsets in that array. Possible, but very unsane.
Fortunately, all offsets in this case are known at compile time, no runtime calculations. > I've applied it to one of tree copies last week and always updated from > svn w/o problems. Could you explain the purpose of these *_32bits_m() functions, please?.. >> There is no need to force your code (engine) to work with any kind of >> buffer or return >> a buffer with any user's format. Engine can return its buffers in own format >> and then it >> is up to user - work with them as via official interface is or to convert it >> into >> something more suitable. > > Exactly this is done now. Now conversions are performed too early - in yvalve. It is not in the best position for such things because it is not aware of the best format for each provider (which may differ). -- WBR, SD. ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
