oship-dev team mailing list archive
-
oship-dev team
-
Mailing list archive
-
Message #01201
[Bug 609142] [NEW] In class CodePhrase initializer, is it it necessary to test for the argument types?
Public bug reported:
In class CodePhrase initializer, is it it necessary to test for the
argument types?
** Affects: oship
Importance: Low
Status: New
** Changed in: oship
Importance: Undecided => Low
** Changed in: oship
Milestone: None => 1.5
--
In class CodePhrase initializer, is it it necessary to test for the argument types?
https://bugs.launchpad.net/bugs/609142
You received this bug notification because you are a member of OSHIP
Development Team, which is subscribed to Open Source Health Information
Platform.
Status in Open Source Health Information Platform (OSHIP): New
Bug description:
In class CodePhrase initializer, is it it necessary to test for the argument types?
Follow ups
-
[Bug 609142] Re: In class CodePhrase initializer, is it it necessary to test for the argument types?
From: Diego Manhães Pinheiro, 2011-02-14
-
[Bug 609142] Re: In class CodePhrase initializer, is it it necessary to test for the argument types?
From: Diego Manhães Pinheiro, 2011-02-14
-
[Bug 609142] Re: In class CodePhrase initializer, is it it necessary to test for the argument types?
From: Eduardo César, 2010-08-06
-
[Bug 609142] Re: In class CodePhrase initializer, is it it necessary to test for the argument types?
From: Eduardo César, 2010-08-06
-
[Bug 609142] Re: In class CodePhrase initializer, is it it necessary to test for the argument types?
From: Eduardo César, 2010-08-06
-
[Bug 609142] Re: In class CodePhrase initializer, is it it necessary to test for the argument types?
From: Eduardo César, 2010-08-06
-
[Bug 609142] [NEW] In class CodePhrase initializer, is it it necessary to test for the argument types?
From: Sergio Miranda Freire, 2010-07-23
References