> I was not using Makefile on purpose because I want to know exactly what I
> am doing wrong
That's exactly the reason why I would avoid doing many suspicious
things at a time.
> (anyway - make in src/tutorial leads in the ver 6.4.2 to
> errors due to inconsitency in header files - starting with missing
> declaration of char16 type).
Makefile is not the cause. Example sources are at least one version
out of date, but Makefile itself is bullet-proof.
> From what you wrote I guess you also do not know how to link something to
> postgres?
If by "something" you mean a c++ code, then I don't know. I doubt
anyone succeeded in doing that. However, plain old c is a real plug-n'play.
> Have anyone on this list ever tried it?
There have been more than a few reports from the list users about
adding user-defined functions written in c. Adding types is not so
popular. I can hardly remember two or three successful attempts, other
than mine (see for example http://wit.mcs.anl.gov/~selkovjr/seg-type.tgz)
> Everything is OK when I add a new column of the new type in the table as a
> LAST one. Troubles come when I need to have another column behind it (of
> the same type, for instance).
I can only speculate about the cause, since I didn't have chance to
see your code. What you describe here appears like a memory leak to
me. Be sure to declare an appropriate size for your type, like so:
CREATE TYPE seg (
internallength = 12,
input = seg_in,
output = seg_out
);
or
CREATE TYPE ndbox (
internallength = variable,
input = ndbox_in,
output = ndbox_out
);
if it is a variable-length type (complete example is in
http://wit.mcs.anl.gov/~selkovjr/ndbox.tgz)
Other than that, watch your source for correct allocation and freeing
of memory. (If I recall, it is one of those things that make c++
uselsess).
> I do not understand the folowing line:
> > I'm just curious: how do I decode base64 attachments?
> I attached the files to the message in pine and do not know anything about
> base64 nor found a mention in man pages.
Don't know how to deal with attachments, unless they are clear text or
uuencoded. What could be the reason for encoding the c source?
--Gene
