Re: Re: Re: sybperl2.14 compile opcode error

Correct - but depending on the type of shop where you are, and the type of work you need to do sybperl (as in Sybase::CTlib) may be preferable.

And as you saw portability depends a lot on SQL code that you use, and with Sybase any large project will use stored procedures, which means that the SQL is probably portable to MS-SQL, but not to anything else (at least not easily).

And choice is good. :-)

Michael

Comment on Re: Re: Re: sybperl2.14 compile opcode error

Replies are listed 'Best First'.
Re: Re: Re: Re: sybperl2.14 compile opcode error by trowa (Acolyte) on Apr 17, 2002 at 20:59 UTC
Thanks for all the replies, my guess was also that it was not a source code or perl issue. I just needed a little confirmation on that. Also, I appreciate all the sybperl work you are doing Michael, I am using your module on a daily basis in a production environment (1 Sun E5500, 1 Sun E4500, 4 Sun E3500's). We are mostly running sybase over here, so portability is not such an issue. I've never run into any problems using Sybase::CTlib on solaris 2.6, only solaris 8--and I blame my lack of knowledge when it comes to the configuration of compilers. Anyways, next time I'll post threads like this to the sybperl groups as it is not a perl issue. I've mentioned several times to the management team over here how useful perlmonks has been, and the debts we owe to Michael Peppler. Unfortunatly, it seems bean-counters always seem to have the final say in things... if I can get them to buy in on contracting consulting, I'll get in touch with you Michael...	[reply]

Replies are listed 'Best First'.

Re: Re: Re: Re: sybperl2.14 compile opcode error
by trowa (Acolyte) on Apr 17, 2002 at 20:59 UTC

Thanks for all the replies, my guess was also that it was not a source code or perl issue. I just needed a little confirmation on that. Also, I appreciate all the sybperl work you are doing Michael, I am using your module on a daily basis in a production environment (1 Sun E5500, 1 Sun E4500, 4 Sun E3500's). We are mostly running sybase over here, so portability is not such an issue. I've never run into any problems using Sybase::CTlib on solaris 2.6, only solaris 8--and I blame my lack of knowledge when it comes to the configuration of compilers. Anyways, next time I'll post threads like this to the sybperl groups as it is not a perl issue. I've mentioned several times to the management team over here how useful perlmonks has been, and the debts we owe to Michael Peppler. Unfortunatly, it seems bean-counters always seem to have the final say in things... if I can get them to buy in on contracting consulting, I'll get in touch with you Michael...

[reply]