From: SourceForge.net <no...@so...> - 2007-06-10 14:16:20
|
Bugs item #1734415, was opened at 2007-06-10 16:16 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101645&aid=1734415&group_id=1645 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: parsing Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Michael Pujos (bubbleguuum) Assigned to: Marcelo Matus (marcelomatus) Summary: C++ parser fails on template code Initial Comment: The C++ fails to parse the following code: template<typename t_item> class alloc_fast { ... } template<typename t_item, template<typename> class t_alloc = pfc::alloc_fast > class list_t : public list_impl_t<t_item,pfc::array_t<t_item,t_alloc> > { }; Especially, what it don't like is "template<typename> class t_alloc = pfc::alloc_fast". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101645&aid=1734415&group_id=1645 |
From: SourceForge.net <no...@so...> - 2007-12-02 12:27:10
|
Bugs item #1734415, was opened at 2007-06-10 16:16 Message generated for change (Comment added) made by gallien You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101645&aid=1734415&group_id=1645 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: parsing Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Michael Pujos (bubbleguuum) Assigned to: Marcelo Matus (marcelomatus) Summary: C++ parser fails on template code Initial Comment: The C++ fails to parse the following code: template<typename t_item> class alloc_fast { ... } template<typename t_item, template<typename> class t_alloc = pfc::alloc_fast > class list_t : public list_impl_t<t_item,pfc::array_t<t_item,t_alloc> > { }; Especially, what it don't like is "template<typename> class t_alloc = pfc::alloc_fast". ---------------------------------------------------------------------- Comment By: Gallien Matthieu (gallien) Date: 2007-12-02 13:27 Message: Logged In: YES user_id=1250875 Originator: NO Hello, I have the exact same problem and have to find a way to do my job in another way (less clean one). This bug is some months old and there has been no reaction. So please can you at least say something about this bug even if you do not have the possibility to fix it in a timely fashion. Thanks in advance ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101645&aid=1734415&group_id=1645 |
From: SourceForge.net <no...@so...> - 2007-12-06 22:38:38
|
Bugs item #1734415, was opened at 2007-06-10 14:16 Message generated for change (Comment added) made by wsfulton You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101645&aid=1734415&group_id=1645 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: parsing Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Michael Pujos (bubbleguuum) >Assigned to: William Fulton (wsfulton) Summary: C++ parser fails on template code Initial Comment: The C++ fails to parse the following code: template<typename t_item> class alloc_fast { ... } template<typename t_item, template<typename> class t_alloc = pfc::alloc_fast > class list_t : public list_impl_t<t_item,pfc::array_t<t_item,t_alloc> > { }; Especially, what it don't like is "template<typename> class t_alloc = pfc::alloc_fast". ---------------------------------------------------------------------- >Comment By: William Fulton (wsfulton) Date: 2007-12-06 22:38 Message: Logged In: YES user_id=242951 Originator: NO Fixed for 1.3.34 ---------------------------------------------------------------------- Comment By: Gallien Matthieu (gallien) Date: 2007-12-02 12:27 Message: Logged In: YES user_id=1250875 Originator: NO Hello, I have the exact same problem and have to find a way to do my job in another way (less clean one). This bug is some months old and there has been no reaction. So please can you at least say something about this bug even if you do not have the possibility to fix it in a timely fashion. Thanks in advance ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101645&aid=1734415&group_id=1645 |
From: Olly B. <ol...@su...> - 2007-06-10 14:25:27
|
On 2007-06-10, SourceForge.net <no...@so...> wrote: > Assigned to: Marcelo Matus (marcelomatus) Sadly Marcelo seems to have ceased active SWIG development - I do hope he's just busy with other things rather than had an accident! But I think at this point it is counter-productive that new bugs are being automatically assigned to him - it gives the wrong impression to users reporting bugs, and makes it harder for developers to see at a glance if a bug is effectively unassigned. Assuming there's general agreement, could somebody with appropriate rights change this? Cheers, Olly |
From: William S F. <ws...@fu...> - 2007-12-12 19:03:18
|
Olly Betts wrote: > On 2007-06-10, SourceForge.net <no...@so...> wrote: > >> Assigned to: Marcelo Matus (marcelomatus) >> > > Sadly Marcelo seems to have ceased active SWIG development - I do hope > he's just busy with other things rather than had an accident! > > But I think at this point it is counter-productive that new bugs are > being automatically assigned to him - it gives the wrong impression to > users reporting bugs, and makes it harder for developers to see at a > glance if a bug is effectively unassigned. Assuming there's general > agreement, could somebody with appropriate rights change this Just spotted this request, so there should now be nothing automatically assigned to Marcelo. William |