perl - Avoid "could not find parserDetail.ini" warning -

-

जब XML :: Simple का उपयोग करते हैं, तो मुझे हमेशा चेतावनी मिलती है 

  /usr/lib/perl5/vendor_perl/5.8.8/XML/SAX

में ParserDetails.ini नहीं मिल सका 

  {कोई चेतावनी qw (insert_your_magic_here); मेरी $ hash_ref = XMLin ('my_file.xml')}

चेतावनी के बारे में मैं लाल प्रतिलिपक और एक 'कैथेगोरी हिस्टी' पाया, लेकिन मुझे नहीं पता कि यह चेतावनी किस श्रेणी में है।

क्या आप जानते हैं?

क्या आप जानते हैं कि उन पार्सडिटरेट्स के लिए क्या इरादा है?

इसके नाम के बावजूद, सही तरीके से काम करना बेहद मुश्किल है, और आप उपयोग या बदले में बेहतर होगा।

XML :: सरल आपको चेतावनी दे रहा है कि कोई प्रयोग करने योग्य SAX पार्सर कॉन्फ़िगरेशन नहीं है। चूंकि SAX विकल्पों की तुलना में तेज़ और अधिक विश्वसनीय है, मैं सुझाव देता हूं कि आप इसका इस्तेमाल करने के लिए XML :: Simple बताएं आप इसे जोड़कर ऐसा कर सकते हैं 

  $ xml :: सरल :: PREFERRED_PARSER = 'XML :: Parser';   
 अपने प्रोग्राम के शीर्ष पर,  एक्सएमएल :: सरल  का उपयोग करने के ठीक बाद। 
 
 आपको  XML को भी इंस्टॉल करना पड़ सकता है :: पार्सर , क्योंकि यह पूर्व स्थापित कोर मॉड्यूल में से एक नहीं है।

Comments

Post a Comment

Popular posts from this blog

apache - 504 Gateway Time-out The server didn't respond in time. How to fix it? -

-
Using a form submission on an embedded iframe , the customer downloads a compressed log file Requested. The request was sent to the server, which is the compressed log files, perform some database operations and returns a compressed file. After just 2 minutes, 504 gateway time-out server did not respond timely message on browser net panel How to fix this error? The log files were taking a long time to compress, and timeout was set to 2min The error was fixed by extending the file file: # # timeout: The number of seconds before getting the time out. # # # Timeout 120 timeout 600
Read more

c# - .net WebSocket: CloseOutputAsync vs CloseAsync -

-
We have a working ASP.NET Web API REST service, which is one of the methods of our controller, HTTPTTEX. .) Socket handler code looks something like this ... Public async task socket handler (AspNetWebSocketContext context) {_webSocket = context.WebSocket; ... while (! Cts.IsCancellationRequested) {WebSocketReceiveResult Results = _webSocket.ReceiveAsync (Input Segment, cts.Token) .Result; WebSocketsStateCollusocketState = _webSocket.State; If (result.MessageType == WebSocketMessageType.Close || currentSocketState == WebSocketState.CloseReceived) {// What should I use. CloseAysnc () or. CloseOutputAsync ()? _webSocket.CloseOutputAsync (WebSocketCloseStatus.NormalClosure, "Client Requested", cts.Token). Wait (); } If (currentSocketState == WebSocketState.Open) {...}}} .What is the difference between .CooseAsync () and CloseOutputAysnc ()? I tried both of them and they both seemed to work fine but some difference should be the same they both describe very similar to...
Read more

c++ - How to properly scale qgroupbox title with stylesheet for high resolution display? -

-
I am trying to apply a stylesheet for QGroupBox (QT4.8), which works on the normal screen ( 96 dpi) high resolution screen (Yoga 2 Pro, 3200x1800, 275 dpi, windows 8.1). The following style looks good on the 275 dpi screen, but the top margins on a regular 96 dpi screen are far too big. QGroupBox {border: 1px solid red; Range radius: 7px; Margin-top: 12x; } QGroupBox :: Title {subcontrol-origin: margin; Subcontrol-position: left above; Padding-left: 10px; Padding-right: 10px; } Changing the top-margin has an effect, but I did not get a proper setting which works on both screens. If I shorten the value, the content of the group box overlaps with the title on 275 dpi screen. I was also playing with units "East", "PX", "MX", "PT". Reading the document I would have guessed, "2 X" was the correct solution, which should be scaled with different screen resolutions. Without the stylesheet, the groupbox works well on both screens. ...
Read more