Re: [Prelude Hybrid IDS] #269: Wrong idmef_*_get_next_* python binding functions?

"Prelude Hybrid IDS" <[email protected]>
Newsgroups gmane.comp.security.ids.prelude.devel
Message-ID <[email protected]>
#269: Wrong idmef_*_get_next_* python binding functions?
------------------------------------+---------------------------------------
 Reporter:  [email protected]  |        Owner:  yoann            
     Type:  defect                  |       Status:  closed           
 Priority:  normal                  |    Milestone:  Libprelude 0.9.17
Component:  libprelude              |      Version:  0.9              
 Severity:  normal                  |   Resolution:  fixed            
 Keywords:  python binding          |  
------------------------------------+---------------------------------------
Changes (by pollux):

  * status:  new => closed
  * resolution:  => fixed

Comment:

 (In [10125]) SWIG bindings: add typemaps to arguments of *_get_next*
 functions,
 to allow NULL arguments, which are forbidden by default by SWIG
 (Fix #269)

-- 
Ticket URL: <https://trac.prelude-ids.org/ticket/269#comment:14>
Prelude Hybrid IDS <http://www.prelude-ids.org>
The Prelude Hybrid Intrusion Detection System suite
_______________________________________________
Prelude-devel site list
[email protected]
http://www.prelude-ids.org/mailman/listinfo/prelude-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.