# Point is ambiguous but complaints are about Appkit Framework code
**URL:** https://forum.juce.com/t/point-is-ambiguous-but-complaints-are-about-appkit-framework-code/49569
**Category:** General JUCE discussion
**Created:** [January 7, 2022, 10:18pm UTC](https://forum.juce.com/t/point-is-ambiguous-but-complaints-are-about-appkit-framework-code/49569 "2022-01-07T22:18:54Z")
**Posts on this page:** 1
**Showing post:** 6
### Author:  [@nicolasdanet](https://forum.juce.com/u/nicolasdanet)
#### Post date: [January 10, 2022, 4:45pm UTC](https://forum.juce.com/t/point-is-ambiguous-but-complaints-are-about-appkit-framework-code/49569/6 "2022-01-10T16:45:01Z")
The “Reference to Point is ambiguous” error is a rather common topic in that forum.
Have you tried to include the macOS system headers in your project before the JUCE ones?
EDIT: Or there is that trick…
> [@Is Point still broken? - reference to Point is ambiguous](https://forum.juce.com/t/is-point-still-broken-reference-to-point-is-ambiguous/39771/2):
>
> This probably means you’ve pulled in a macOS system header yourself somewhere. You’ll need to prefix your points with juce:: or do something like this: #ifdef \_\_APPLE\_\_ #define Point CarbonDummyPointName #import \ #undef Point #endif
> [@\[Solved\] Unknown type name 'CarbonDummyPointName'](https://forum.juce.com/t/solved-unknown-type-name-carbondummypointname/23361):
>
> Hi guys, I’ve been upgrading my code to the juce 5 master and I have the old CarbonDummyPointName workaround in my code which is causing this error. I’ve noticed that most of the usages of this workaround in juce were removed by Timur in early 2016. I haven’t been able to gather why they are no longer necessary though. When I try to remove it for my own code, the old ambiguous Point error comes back. I’ve tried a few things, building 32 and 64 bit, JUCE\_SUPPORT\_CARBON enabled and disabled. …
---
_[View the full topic](https://forum.juce.com/t/point-is-ambiguous-but-complaints-are-about-appkit-framework-code/49569)._