• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[Pawn] y_hooks v4(ish)
#6
(2019-05-21, 02:02 PM)ohmios Wrote:
(2019-05-21, 12:56 PM)Y_Less Wrote: The major problem with new keywords is compatibility - making sure they don't break existing code which ma already use them as function or variable names.



Do what C does with new keywords, the actual new keyword for "foo"?is?_Foo, and to use "foo" as "foo" you have to include foo.h

That said, code using "continue" or "break"?as function or variable names?deserve to be broken.



Well `continue` and `break` are already keywords, so I'm not worried about them, I was more talking about if I were to add a new keyword like `next`.



And I do already do something similar in YSI. `hook` is actually defined as `HOOK__`, and there are various options to enable or disable the custom `hook` keyword (but enabled by default):



https://github.com/pawn-lang/YSI-Include...TY_MODE.md
  Reply


Messages In This Thread
y_hooks v4(ish) - by Y_Less - 2019-05-19, 02:57 PM
RE: y_hooks v4(ish) - by JustMichael - 2019-05-21, 11:57 AM
RE: y_hooks v4(ish) - by Y_Less - 2019-05-21, 12:56 PM
RE: y_hooks v4(ish) - by JustMichael - 2019-05-21, 01:25 PM
RE: y_hooks v4(ish) - by ohmios - 2019-05-21, 02:02 PM
RE: y_hooks v4(ish) - by Y_Less - 2019-05-21, 02:28 PM
RE: y_hooks v4(ish) - by Kar - 2019-05-21, 06:44 PM
RE: y_hooks v4(ish) - by Y_Less - 2019-06-01, 01:17 AM
RE: y_hooks v4(ish) - by Y_Less - 2019-06-01, 02:37 AM
RE: y_hooks v4(ish) - by JustMichael - 2019-06-01, 03:37 PM
RE: y_hooks v4(ish) - by Y_Less - 2019-06-02, 11:56 AM

Forum Jump: