Reply to Re: New *WORKING* cross-platform editor
If you don't have an account, just leave the password field blank.
June 25th 2011, 05:21 AM
shevek
Yes, I agree. The bugs in DinkC are not hard to find, and anyway they are known. What I'm saying (well at least I meant to say that) is that DinkC allows you to create bugs in your code that are hard to find. Such as putting a space in the wrong place. If it wants to make a problem of that, that's fine, but it should shout a sensible error message then (syntax error parsing "a+=3" or something). If it does allow it, that's fine too, but then it should work. There is no feature in such behaviour that allow any cool special things to be done.
My preprocessor doesn't limit anything. You can still write anything you can write in DinkC (well, except goto into another function. I just dislike it too much. If you have a really good use case, I might consider adding it, but it will still give a big fat warning when anybody uses it).
The point is not to create a simplified DinkC, but to be able to write the same things in a sane way.
My preprocessor doesn't limit anything. You can still write anything you can write in DinkC (well, except goto into another function. I just dislike it too much. If you have a really good use case, I might consider adding it, but it will still give a big fat warning when anybody uses it).
The point is not to create a simplified DinkC, but to be able to write the same things in a sane way.
