Xnest: fix analyzer warning on uninitialized `DefaultVisual`
In xnestOpenScreen(), some compilers/analyzers spitting out a false alarm on `defaultVisual` field potentially used uninitialized. This can't practically happen, but not all compilers/analyzers really can see that. Adding a zero initializer doesn't cost us anything, so silencing that false alarm is trivial. Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
This commit is contained in:
		
							parent
							
								
									ccf9787bd6
								
							
						
					
					
						commit
						6a3162d623
					
				| 
						 | 
					@ -164,7 +164,7 @@ Bool
 | 
				
			||||||
xnestOpenScreen(ScreenPtr pScreen, int argc, char *argv[])
 | 
					xnestOpenScreen(ScreenPtr pScreen, int argc, char *argv[])
 | 
				
			||||||
{
 | 
					{
 | 
				
			||||||
    unsigned long valuemask;
 | 
					    unsigned long valuemask;
 | 
				
			||||||
    VisualID defaultVisual;
 | 
					    VisualID defaultVisual = 0;
 | 
				
			||||||
    int rootDepth;
 | 
					    int rootDepth;
 | 
				
			||||||
    miPointerScreenPtr PointPriv;
 | 
					    miPointerScreenPtr PointPriv;
 | 
				
			||||||
 | 
					
 | 
				
			||||||
| 
						 | 
					
 | 
				
			||||||
		Loading…
	
		Reference in New Issue