🚀 go-pugleaf

In article <698@helios.prosys.se>, ath@prosys.se (Anders Thulin) says:
>
>In article <X5Z8u3w163w@turbo.atl.ga.us> greg@turbo.atl.ga.us writes:
>>ath@prosys.se (Anders Thulin) writes:

     <bunch of stuff deleted>

>Well, I sort of agree. I believe the library package is decent. But
>I spend too much time hunting for information, some of which isn't
>even there. As I'm willing to pay for documentation, I'm going to
>use another library for now. But I will certainly be interested in how
>TCXL evolves. That note about event-controlled UI's seems promising ...
>
>-- 
>Anders Thulin       ath@prosys.se   {uunet,mcsun}!sunic!prosys!ath
>Telesoft Europe AB, Teknikringen 2B, S-583 30 Linkoping, Sweden

More comments...

I registered CXL at 5.0 and I really got my money's worth out of it.
Had I been evaluating TCXL to see if I wanted to register it (based on
5.51) I wouldn't have done so.

Not being a "professional" C programmer, there are things that I'm having
a hard time with. 

He is using loads and loads of #defines throughout the library. He wants
me to use ChrP for char *, NOARG for void, CTyp for something I still
haven't figured out yet. Virtually every (what do you call them?) int, char
char *, far etc are redefined and he says that I will like them better after
I use them. 

&*($@ he changed the fill_() function to use some sort of struct union
something or other. I can't seem to get it to work. I assume that it's 
something like the first 4 bits are the row and the last 4 bits are the
column, but I can't get them built correctly. It references VposT which
I can't seem to figure out (it's in TCXL-USE.txt if you wish to look and
explain). There are other functions that use this type of variable. 

Jeeze, I really got a headache on Friday when I was trying to figure it
out.

I know, I know, bitch bitch bitch. "Why do you use it if you don't like it?"

It's still a great package. There are loads of functions that I will use and
some of the functions have been expanded upon. I will probably never 
use the full capability of the library now. It seems like he's trying to 
write professional librarys for hobby programmers (IMHO). Although,
how many professional programmers out there will want to change
their programming style just to use these functions???

Carl Schelin
tcs@mailer.jhuapl.edu