Skip to content

Commit 484479d

Browse files
committed
[SyntaxParser] Remove leftover type declaration and adjust the *_EXPORTS macro name
Also fixup some doc-comments.
1 parent 8f4bb24 commit 484479d

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

include/swift-c/SyntaxParser/SwiftSyntaxParser.h

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@
5555

5656
#ifndef SWIFTPARSE_PUBLIC
5757
# ifdef _WIN32
58-
# ifdef SwiftSyntaxParser_EXPORTS
58+
# ifdef libSwiftSyntaxParser_EXPORTS
5959
# define SWIFTPARSE_PUBLIC __declspec(dllexport)
6060
# else
6161
# define SWIFTPARSE_PUBLIC __declspec(dllimport)
@@ -126,7 +126,6 @@ typedef struct {
126126
//=== Parser Functions ----------------------------------------------------===//
127127

128128
typedef void *swiftparse_parser_t;
129-
typedef void *swiftparse_alloc_t;
130129

131130
SWIFTPARSE_PUBLIC swiftparse_parser_t
132131
swiftparse_parser_create(void);
@@ -168,13 +167,13 @@ typedef swiftparse_lookup_result_t
168167
/// It is not required to set a \c swiftparse_node_lookup_t block before calling
169168
/// \c swiftparse_parse_string. Not setting a \c swiftparse_node_lookup_t block
170169
/// has same semantics as never skipping any source regions.
171-
/// \c swiftparse_node_lookup_t can be called multiple times to change the block
172-
/// before subsequent parses.
170+
/// \c swiftparse_parser_set_node_lookup can be called multiple times to change
171+
/// the block before subsequent parses.
173172
SWIFTPARSE_PUBLIC void
174173
swiftparse_parser_set_node_lookup(swiftparse_parser_t,
175174
swiftparse_node_lookup_t);
176175

177-
/// Parse the provided \c source and invoke the callback that was set via
176+
/// Parse the provided \p source and invoke the callback that was set via
178177
/// \c swiftparse_parser_set_node_handler as each syntax node is parsed.
179178
///
180179
/// Syntax nodes are provided in a top-bottom, depth-first order. For example,

0 commit comments

Comments
 (0)