Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 0.1.1
Bug #16415 Undefined Index Notices In Net/HL7/Message.php
Submitted: 2009-07-08 02:00 UTC
From: acarlisle Assigned: doconnor
Status: Closed Package: Net_HL7 (version 0.1.0)
PHP Version: 5.2.5 OS: CentOS
Roadmaps: (Not assigned)    
Subscription  


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 48 + 21 = ?

 
 [2009-07-08 02:00 UTC] acarlisle (Aaron Carlisle)
Description: ------------ If you use the constructor without passing an array of globals, a bunch of Undefined Index notices are returned. I fixed this by changing the existence check to an isset(). Test script: --------------- $message = new Net_HL7_Message(); Expected result: ---------------- No errors. Actual result: -------------- Notice: Undefined index: SEGMENT_SEPARATOR in HL7/Message.php on line ... Notice: Undefined index: FIELD_SEPARATOR in HL7/Message.php on line ... Notice: Undefined index: COMPONENT_SEPARATOR in HL7/Message.php on line ... Notice: Undefined index: SUBCOMPONENT_SEPARATOR in HL7/Message.php on line ... Notice: Undefined index: REPETITION_SEPARATOR in HL7/Message.php on line ... Notice: Undefined index: ESCAPE_CHAR in HL7/Message.php on line ... Notice: Undefined index: HL7_VERSION in HL7/Message.php on line ...

Comments

 [2009-07-16 05:29 UTC] doconnor (Daniel O'Connor)
Unfortunately, you might have to raise a bug in their bug tracker too. https://sourceforge.net/tracker/?func=browse&group_id=53886&atid=471943
 [2009-07-27 20:23 UTC] doconnor (Daniel O'Connor)
-Status: Open +Status: Closed -Assigned To: +Assigned To: doconnor
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.