Re: Open Call for DOS Developers

new topic     » goto parent     » topic index » view thread      » older message » newer message

It doesn't matter what I think or say. 
 
There are 3906 views of this DOS subject, the next DOS subject has 215 views, and 
the next DOS subject has 657 views. 
 
I saw the Call for DOS Developers and I looked at the source code and 
tried to run the archive source code and it had many errors. 
 
So I tried to help remove the errors but did not know about all the changes 
that had been made to the build procedures. 
 
I followed directions exactly that I was given step by step until the source 
could be compiled. 
 
Because I could not understand all the changes I was criticized for not 
understanding the code and should have been able to solve the problems quickly. 
 
I never claimed to be a wizard, a mind reader or a Developer. 
 
I maybe 77 years old but I am not stupid or too old to think. 
 
I've been working with computer hardware, software, and electronics for 60 years 
from mechanical analog up to present day computers. 
 
If someone reads the source.doc in the source directory. It doesn't explain how 
to work on the latest source code. I've have features that I've been able to 
add to the pure euphoria but not to the real source.  
 
There is no written documentation to explain how to add a feature to today's 
source code. 
 
There is no written explanation of how to pass calls between the frontend and backend. 
 
Matt gave a example to me that I could do it by backend.e using machine function 65. 
 
But I could find no examples in the source that actually did that. 
 
User's have always contributed to features but they can not do it; if only the 
developers know how the source basically works. 
 

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu