In other words I don't want to declare. An easy way to avoid writing declares is to use a simple utility program to do it for you. It takes a few lines of code to scan your program for all the sub and function statements, and output them to a text file in the form of declare statements. The resulti...

"There are millions of lines of COBOL code still in use today and that ONE program should be retired." In all seriousness, though that is an impressive bit of code. Good job. Thanks for the compliment. And don't worry about the COBOL joke, we old-time COBOL programmers have heard them all...

Back in the late 1970's and early 1980's, when personal computers were appearing, I created a COBOL-like language to allow me to write ASM programs in psuedo code. Here's a small example of some code that's still in use today, exactly as shown. It's part of a series of MSDOS COBOL80 business applica...

@ike This is very nice! You can rotate icons on buttons........It took me couple hrs to design some icons and then I figured out this trick MOVROT.btn7 = Fl_ButtonNew(50, 30, 40, 40, "@#+97>>") http://www.csounds.com/manual/html/FLbutton.html I don't program in Python, but I've found the f...

The only point to this thread was that BASIC was meant for those who do not have the time or computer science background to deal with a complicated language or complex (to them) need for setups. If a language or its extensions have syntax challenges then I see that as a negative for the language. Y...

BASIC defined as an easy to learn, read and understandable computer language hasn't changed.. Actually, things changed very soon after the language was invented. -- it has always been evolving. With the advent of minicomputers in the early 1970s, BASIC became a business oriented language that suppo...

Also I notice that some programmers (they claim to be about 5% of all programmers) have a negative view to all the OO hype, this being one of them, https://www.youtube.com/watch?v=QM1iUe6IofM. An interesting discussion, and one that seems to agree with my 5 rules of OOP. In general I avoid OOP, but...

It is just that it seems to me from reading about OO in other languages including VB.NET that it shouldn't be all that hard with tricky syntax to trip you up. OO should be a means to easily solve a problem not a problem to be solved. Hi BC2 Once again I agree with you, but the trick to using OOP is...

A language passes that test to the extent it mimics a real human language and doesn't make use of exotic or special purpose symbols and idiosyncratic ways of expressing an idea. The closer to a plain human language the better in my opinion. You could always program in COBOL. But even COBOL has evol...

I need to convert from PowerBasic, is there a guide to help me to do this ? Not that I've ever seen. One pretty much has to dive in and start converting, but luckily, the two languages are very similar. Often, it's just minor syntax or spelling differences. For instance, PB uses the $ sign on a key...

Thanks Joshy

Joshy I really like the new commands. It's so much easier than playing with hidden fltk structures. However, I think there's an error in the following declares: ' Set/Get a user-data value for the item. declare sub Fl_Tree_ItemSetUserData(byval item as Fl_Tree_Item ptr, byval userdata as any ptr) de...

Joshy

There's a potentially recursive wrapper bug in fltk-c.bi -- the link points to the obsolete forum topic. :-)

Please report all FLTK C wrapper bugs and problems on the following page:
http://freebasic.net/forum/viewtopic.php?f=14&t=21548

Rod

Thanks Joshy

Rod

Joshy

I've just downloaded the latest Linux fltk-c-1.3.3.zip, but I'm not seeing any lib*.so files. Am I missing something on account of my extreme old age?

Thanks

Rod