Sub / Function can be on one line, but only if there's brackets.
```
| Storage_opt tFUNCTION Identifier ArgumentsDecl BodyStatements tEND tFUNCTION
```
This leads to sometimes to `link_statements` being called with `head` being NULL, probably because now the `:` can be parsed as `Statement` in `BodyStatements`.
Also note that this introduces another shift/reduce conflict, could be related, but I don't understand it well enough. Feedback would be appreciated, I'm still learning bison.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/3206
Required for !1857 to not break when comctl32 version 6 isn't requested by application (in particular, found this in [qapitrace](https://github.com/apitrace/apitrace)).
Manifest resource id and assembly identity name match with Windows.
For isolation purposes, activation context is disabled while emitting events.
--
v12: comdlg32: Enable visual styles when showing IFileDialog.
https://gitlab.winehq.org/wine/wine/-/merge_requests/2068
On Fri Jun 30 17:01:00 2023 +0000, Zebediah Figura wrote:
> So in isolation I think the solution proposed by this patch set is fine,
> and even looks prettiest. *But* what I remember from that discussion—and
> Henri will undoubtedly be able to express this more eloquently—is that
> the concern is
> (a) we might want to do something more complicated than just
> vkQueuePresent()—cf. the issues about fullscreen window styles /
> presenting to the client rect. I'm not sure but this might also turn out
> to be an issue for DirectComposition.
> (b) we might want to plumb presentation through D3DKMTPresent() [which
> may be necessary to achieve the above], and it will probably not be
> possible to do any vkd3d calls from the Unix side.
I pushed a new implementation incorporating the changes you're suggesting, and honestly I don't dislike it: https://gitlab.winehq.org/giomasce/wine/-/commits/chianti (only the last three commits changed in a meaningful way; or maybe at all). With this implementation it should be relatively easy to present with whatever API is available, though I don't really know how the options you mention work, so maybe there is some additional complexity I'm not aware of.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/3165#note_37623
In a declaration with multiple variables, the variables must be created
before the initializer of the next variable is parsed. This is required
for initializers such as:
```
float a = 1, b = a, c = b + 1;
```
The solution is to parse the type information in the same rule as the first variable ('a' in this case) so that it can be declared before the parser reaches the initializer for the following variables.
To initialize the following variables, the type information is passed along from the first variable's struct parse_variable_def to the next and so on.
---
Solves https://bugs.winehq.org/show_bug.cgi?id=54484, pointed out by @nsivov.
--
v3: vkd3d-shader/hlsl: Declare vars individually when parsing struct declarations.
vkd3d-shader/hlsl: Declare vars individually when parsing regular declarations.
vkd3d-shader/hlsl: Split declare_vars().
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/250