We have an IRC Channel!

Opinions, ideas and thoughts about Nekochan Net.
User avatar
foetz
Moderator
Moderator
Posts: 6484
Joined: Mon Apr 14, 2003 4:34 am
Contact:

Re: We have an IRC Channel!

Unread postby foetz » Thu Feb 12, 2015 8:39 pm

vishnu wrote:it totally pukes with g++ current

you realize that there're also other compilers? :P
anyway made me curious now, gonna check it out :D

btw how about xchat? the gtk1 version is nice

User avatar
vishnu
Donor
Donor
Posts: 3073
Joined: Sun Mar 18, 2007 3:25 pm
Location: Minneapolis, Minnesota USA

Re: We have an IRC Channel!

Unread postby vishnu » Thu Feb 12, 2015 9:00 pm

Oh sure, there are tons of perfectly worthy IRC clients, it's just that as a decades long Motif hacker I greatly prefer Motif applications. So really the problem is me not the clients that are available, which are legion...

For the smirc source code, I can get 10 of the 27 c plus plus files in the widget subdirectory to compile. He's got all the widget code wrapped into a plethora of classes that he apparently wrote all by himself, or, probably more likely wrote for a paying client and then he used the classes to create smirc. Either way truly a monumental task. And of course now the language standard has evolved to the point where the compilers won't compile it, vis:

Code: Select all

make widgetfr.o
c++ -DPACKAGE=\"widget\" -DVERSION=\"0.10\" -DHAVE_DIRENT_H=1 -DSTDC_HEADERS=1 -DHAVE_UNISTD_H=1 -DHAVE_STRINGS_H=1  -I. -I.      -I./.. -I./../afx -g -O2 -Wall -c widgetfr.C
widgetfr.C: In member function 'void COptionMenuWidgetExtended::Create(CWidget*)':
widgetfr.C:61:63: error: conversion from 'int' to 'CWidgetAttach' is ambiguous
widget.h:220:2: note: candidates are: CWidgetAttach::CWidgetAttach(void*)
widget.h:218:2: note:                 CWidgetAttach::CWidgetAttach(long int)
widgetfr.C:64:69: error: conversion from 'int' to 'CWidgetAttach' is ambiguous
widget.h:220:2: note: candidates are: CWidgetAttach::CWidgetAttach(void*)
widget.h:218:2: note:                 CWidgetAttach::CWidgetAttach(long int)
widgetfr.C: In constructor 'CFileRequesterWidget::CFileRequesterWidget(const char*)':
widgetfr.C:88:6: error: 'void COptionMenuWidgetExtended::OnOptionActivate()' is private
widgetfr.C:131:35: error: within this context
widgetfr.C:131:35: error: no match for 'operator=' in '((CFileRequesterWidget*)this)->CFileRequesterWidget::m_ok = &COptionMenuWidgetExtended::OnOptionActivate'
widgetredirect.h:40:7: note: candidates are: void CActivateRedirect<Base, T>::operator=(T*) [with Base = CPushButtonWidget, T = CFileRequesterWidget]
widgetredirect.h:41:7: note:                 void CActivateRedirect<Base, T>::operator=(void (T::*)()) [with Base = CPushButtonWidget, T = CFileRequesterWidget]
widgetredirect.h:29:69: note:                 CActivateRedirect<CPushButtonWidget, CFileRequesterWidget>& CActivateRedirect<CPushButtonWidget, CFileRequesterWidget>::operator=(const CActivateRedirect<CPushButtonWidget, CFileRequesterWidget>&)
widgetfr.C:95:6: error: 'virtual void COptionMenuWidgetExtended::OnActivate()' is private
widgetfr.C:132:39: error: within this context
widgetfr.C:132:39: error: no match for 'operator=' in '((CFileRequesterWidget*)this)->CFileRequesterWidget::m_cancel = &COptionMenuWidgetExtended::OnActivate'
widgetredirect.h:40:7: note: candidates are: void CActivateRedirect<Base, T>::operator=(T*) [with Base = CPushButtonWidget, T = CFileRequesterWidget]
widgetredirect.h:41:7: note:                 void CActivateRedirect<Base, T>::operator=(void (T::*)()) [with Base = CPushButtonWidget, T = CFileRequesterWidget]
widgetredirect.h:29:69: note:                 CActivateRedirect<CPushButtonWidget, CFileRequesterWidget>& CActivateRedirect<CPushButtonWidget, CFileRequesterWidget>::operator=(const CActivateRedirect<CPushButtonWidget, CFileRequesterWidget>&)
widgetfr.C: In member function 'void CFileRequesterWidget::Create(CWidget*)':
widgetfr.C:157:21: error: conversion from 'int' to 'CWidgetAttach' is ambiguous
widget.h:220:2: note: candidates are: CWidgetAttach::CWidgetAttach(void*)
widget.h:218:2: note:                 CWidgetAttach::CWidgetAttach(long int)
widgetfr.C:158:66: error: conversion from 'int' to 'CWidgetAttach' is ambiguous
widget.h:220:2: note: candidates are: CWidgetAttach::CWidgetAttach(void*)
widget.h:218:2: note:                 CWidgetAttach::CWidgetAttach(long int)
widgetfr.C:160:65: error: conversion from 'int' to 'CWidgetAttach' is ambiguous
widget.h:220:2: note: candidates are: CWidgetAttach::CWidgetAttach(void*)
widget.h:218:2: note:                 CWidgetAttach::CWidgetAttach(long int)
widgetfr.C:164:10: error: conversion from 'int' to 'CWidgetAttach' is ambiguous
widget.h:220:2: note: candidates are: CWidgetAttach::CWidgetAttach(void*)
widget.h:218:2: note:                 CWidgetAttach::CWidgetAttach(long int)
widgetfr.C:167:67: error: conversion from 'int' to 'CWidgetAttach' is ambiguous
widget.h:220:2: note: candidates are: CWidgetAttach::CWidgetAttach(void*)
widget.h:218:2: note:                 CWidgetAttach::CWidgetAttach(long int)
widgetfr.C:179:68: error: conversion from 'int' to 'CWidgetAttach' is ambiguous
widget.h:220:2: note: candidates are: CWidgetAttach::CWidgetAttach(void*)
widget.h:218:2: note:                 CWidgetAttach::CWidgetAttach(long int)
widgetfr.C:184:66: error: conversion from 'int' to 'CWidgetAttach' is ambiguous
widget.h:220:2: note: candidates are: CWidgetAttach::CWidgetAttach(void*)
widget.h:218:2: note:                 CWidgetAttach::CWidgetAttach(long int)
widgetfr.C:190:71: error: conversion from 'int' to 'CWidgetAttach' is ambiguous
widget.h:220:2: note: candidates are: CWidgetAttach::CWidgetAttach(void*)
widget.h:218:2: note:                 CWidgetAttach::CWidgetAttach(long int)
widgetfr.C:192:68: error: conversion from 'int' to 'CWidgetAttach' is ambiguous
widget.h:220:2: note: candidates are: CWidgetAttach::CWidgetAttach(void*)
widget.h:218:2: note:                 CWidgetAttach::CWidgetAttach(long int)
widgetfr.C:197:63: error: conversion from 'int' to 'CWidgetAttach' is ambiguous
widget.h:220:2: note: candidates are: CWidgetAttach::CWidgetAttach(void*)
widget.h:218:2: note:                 CWidgetAttach::CWidgetAttach(long int)
widgetfr.C:198:67: error: conversion from 'int' to 'CWidgetAttach' is ambiguous
widget.h:220:2: note: candidates are: CWidgetAttach::CWidgetAttach(void*)
widget.h:218:2: note:                 CWidgetAttach::CWidgetAttach(long int)
make: *** [widgetfr.o] Error 1


At which point I gave up... :oops:
Project:
Temporarily lost at sea...
Plan:
World domination! Or something...

:Tezro: :Octane2:

User avatar
foetz
Moderator
Moderator
Posts: 6484
Joined: Mon Apr 14, 2003 4:34 am
Contact:

Re: We have an IRC Channel!

Unread postby foetz » Thu Feb 12, 2015 11:02 pm

alrighty, gave it a try ...
first stop: messed up configure script that thinks it needs to add a -L/usr/lib to the LDFLAGS which then of course makes ld32 fail.
next stop: exceptions. disabled them by default of course but the nice little proggy is using them everywhere.
third: the always illusive redefinition of a default argument
4th: TraitP.h missing.

and there it ended for me already. guess my motif is too old :-|

User avatar
Raion-Fox
Donor
Donor
Posts: 1251
Joined: Thu Jan 30, 2014 5:01 pm
Location: near King George, Virginia
Contact:

Re: We have an IRC Channel!

Unread postby Raion-Fox » Thu Feb 12, 2015 11:04 pm

Vishnu, seriously, try irssi out. Its a good terminal-based client and it works well.
:O3x02L: R16000 700MHz 8GB RAM kanna
:Octane: R12000 300MHz SI 896MB RAM yuuka
:Octane2: R12000A 400MHz V6 2.5GB RAM
:Indy: (Acclaim) R4600 133MHz XL Graphics 32MB RAM
:Indy: (Challenge S) R4600 133MHz (MIPS III Build Server)
:O2: R10000 225MHz 256MB RAM 15k 147GB HDD suzuha
Thinkpad W530 i7 3940XM 3GHz, 32GB, K1000M FreeBSD 11/Windows 7 rin
Acer Aspire 5157 (headless) 4GB, FreeBSD 11 kuran
Thinkpad R40 Pentium M 1.5GHz 2GB RAM kasha

User avatar
hamei
Posts: 10427
Joined: Tue Feb 24, 2004 4:10 pm
Location: over the rainbow

Re: We have an IRC Channel!

Unread postby hamei » Fri Feb 13, 2015 2:24 am

vishnu wrote:Oh sure, there are tons of perfectly worthy IRC clients, it's just that as a decades long Motif hacker I greatly prefer Motif applications.

Someone here at the 'chan started on a Motif instant-chat / irc client. He got through two or three versions. It works, I used it a little. As a Motif programmer, vish ... :D
dipshit's a dirty bird .... hamei's not grungy, he's bitchin'

User avatar
vishnu
Donor
Donor
Posts: 3073
Joined: Sun Mar 18, 2007 3:25 pm
Location: Minneapolis, Minnesota USA

Re: We have an IRC Channel!

Unread postby vishnu » Fri Feb 13, 2015 12:21 pm

So much code to compile, so little time... :shock:
Project:
Temporarily lost at sea...
Plan:
World domination! Or something...

:Tezro: :Octane2:

User avatar
foetz
Moderator
Moderator
Posts: 6484
Joined: Mon Apr 14, 2003 4:34 am
Contact:

Re: We have an IRC Channel!

Unread postby foetz » Fri Feb 13, 2015 12:51 pm

vishnu wrote:Is anybody on the irc channel these days?

i am right now :D

User avatar
vishnu
Donor
Donor
Posts: 3073
Joined: Sun Mar 18, 2007 3:25 pm
Location: Minneapolis, Minnesota USA

Re: We have an IRC Channel!

Unread postby vishnu » Fri Feb 13, 2015 9:05 pm

foetz wrote:next stop: exceptions. disabled them by default of course but the nice little proggy is using them everywhere.

foetz, how do you disable exceptions? If I may be so bold as to enquire... :P
Project:
Temporarily lost at sea...
Plan:
World domination! Or something...

:Tezro: :Octane2:

User avatar
foetz
Moderator
Moderator
Posts: 6484
Joined: Mon Apr 14, 2003 4:34 am
Contact:

Re: We have an IRC Channel!

Unread postby foetz » Sat Feb 14, 2015 12:42 am

vishnu wrote:foetz, how do you disable exceptions? If I may be so bold as to enquire... :P

ha, be my guest :P
it's just a compiler flag which, surprise, depends on each compiler. for example:

Code: Select all

MIPSpro >= 7: -LANG:exceptions=OFF
Sun: -noex
...


always part of my default CXXFLAGS on all systems since as you know exceptions cause a significant performance loss

User avatar
vishnu
Donor
Donor
Posts: 3073
Joined: Sun Mar 18, 2007 3:25 pm
Location: Minneapolis, Minnesota USA

Re: We have an IRC Channel!

Unread postby vishnu » Sat Feb 14, 2015 11:31 am

And yet Bjarne considers exception handling to be one of the crowning achievements of c plus pus ... :lol:
Project:
Temporarily lost at sea...
Plan:
World domination! Or something...

:Tezro: :Octane2:

User avatar
duck
Donor
Donor
Posts: 716
Joined: Mon Oct 27, 2003 5:22 pm
Location: Jakobstad, Finland
Contact:

Re: We have an IRC Channel!

Unread postby duck » Sat Feb 14, 2015 1:22 pm

Hmm, irssi builds just fine on IRIX. If irc.nekochan.net would suddenly get an ipv6 address, I'd love to join ;-)
:Octane: halo, octane Image knightrider, d i g i t a l AlphaPC164, pond, soekris net6501, misc cool stuff in a rack
N.B.: I tend to talk out of my ass. Do not take it too seriously.

User avatar
Raion-Fox
Donor
Donor
Posts: 1251
Joined: Thu Jan 30, 2014 5:01 pm
Location: near King George, Virginia
Contact:

Re: We have an IRC Channel!

Unread postby Raion-Fox » Sat Feb 14, 2015 3:13 pm

Are you ipv6 only now duck? I'm still stuck on ipv4 here in Virginia with Verizon FiOS.
:O3x02L: R16000 700MHz 8GB RAM kanna
:Octane: R12000 300MHz SI 896MB RAM yuuka
:Octane2: R12000A 400MHz V6 2.5GB RAM
:Indy: (Acclaim) R4600 133MHz XL Graphics 32MB RAM
:Indy: (Challenge S) R4600 133MHz (MIPS III Build Server)
:O2: R10000 225MHz 256MB RAM 15k 147GB HDD suzuha
Thinkpad W530 i7 3940XM 3GHz, 32GB, K1000M FreeBSD 11/Windows 7 rin
Acer Aspire 5157 (headless) 4GB, FreeBSD 11 kuran
Thinkpad R40 Pentium M 1.5GHz 2GB RAM kasha

User avatar
foetz
Moderator
Moderator
Posts: 6484
Joined: Mon Apr 14, 2003 4:34 am
Contact:

Re: We have an IRC Channel!

Unread postby foetz » Sat Feb 14, 2015 4:10 pm

vishnu wrote:And yet Bjarne considers exception handling to be one of the crowning achievements of c plus pus ... :lol:

given that most of c++ is redundant bloat it fits in just fine from the c++ point of view :P

robespierre
Posts: 1476
Joined: Mon Sep 12, 2011 2:28 pm
Location: Boston

Re: We have an IRC Channel!

Unread postby robespierre » Sat Feb 14, 2015 6:03 pm

The exception support in C++ is half-baked, it doesn't allow for exceptions that are continuable.
Specifically, there are two ways to implement an exception system: either the stack is unwound to the point of the exception handler first, losing all inferior context; or the stack is searched for a handler but not unwound. in the latter case, the handler can adjust the signaling context and then tell it to continue. This is how Xerox's Cedar Mesa exceptions worked.
:PI: :O2: :Indigo2IMP: :Indigo2IMP:

User avatar
vishnu
Donor
Donor
Posts: 3073
Joined: Sun Mar 18, 2007 3:25 pm
Location: Minneapolis, Minnesota USA

Re: We have an IRC Channel!

Unread postby vishnu » Sat Feb 14, 2015 8:28 pm

robespierre wrote:The exception support in C++ is half-baked, it doesn't allow for exceptions that are continuable.
Specifically, there are two ways to implement an exception system: either the stack is unwound to the point of the exception handler first, losing all inferior context; or the stack is searched for a handler but not unwound. in the latter case, the handler can adjust the signaling context and then tell it to continue. This is how Xerox's Cedar Mesa exceptions worked.


Yes but the guy who created Cedar Mesa exceptions said, at the C++ standardization meeting in 1991, “termination is preferred over resumption; this is not a matter of opinion but a matter of years of experience. Resumption is seductive, but not valid.”

Wiki article: in the "Termination semantics" section.
Project:
Temporarily lost at sea...
Plan:
World domination! Or something...

:Tezro: :Octane2:


Return to “Nekochan Net”

Who is online

Users browsing this forum: No registered users and 1 guest