Good to see it working.
Where do I find the announcements of changes to the VM?
In Pharo-Dev there are the nice mails by Marcus for the image changes.
Stephan
Stéphane Ducasse writes:
> Thanks for your feedback.
> We would love to provide a better infrastructure. It just takes time.
Well I remember Matinez writing about hacking the vm. Something about
how to debug the VM and libraries and FFI, would have helped me (I
guess) I'm not that afraid of C but
Thanks for your feedback.
We would love to provide a better infrastructure. It just takes time.
Stef
On Jul 4, 2013, at 12:02 PM, Friedrich Dominicus
wrote:
> To everyone intersted/involved. I downloaded a new virtual machine today
> and the same code which has crashed the virtual machine, sim
To everyone intersted/involved. I downloaded a new virtual machine today
and the same code which has crashed the virtual machine, simply works on
the new Virtual machine. The machine I'm using is:
'NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid:
acc98e51-2fba-4841-a965-2975997bba66
On 24 June 2013 22:28, jtuc...@objektfabrik.de wrote:
> You're joking, right?
>
No. As you notice, it has the functionality of a comment. Probably from
someone who is not used to versioning systems.
In C you'd use #ifdef 0 ... #endif, which is quite common.
--
Milan Mimica
http://sparklet.sf.
"jtuc...@objektfabrik.de" writes:
> That's the way we all do it, right?
> So are you saying ODBC in Pharo 1.x still works on that very same
> machine?
Nope I checked.
>Does ldd for the old VM yield the same kind of output?
Well the all find the libraries. But Pharo 1.4 even has different share
Am 25.06.13 07:10, schrieb Friedrich Dominicus:
"jtuc...@objektfabrik.de" writes:
Hi Friedrich,
I guess what could help people understand more about what the actual
differences might be is if you can exactly say under which Pharo
version and on which VM your ODBC connection had been working
b
"jtuc...@objektfabrik.de" writes:
> Hi Friedrich,
>
> I guess what could help people understand more about what the actual
> differences might be is if you can exactly say under which Pharo
> version and on which VM your ODBC connection had been working
> before. Was it also on a 64 bit lInux? Ev
Albert Einstein)
From: "jtuc...@objektfabrik.de"
To: pharo-users@lists.pharo.org
Sent: Monday, June 24, 2013 4:28:50 PM
Subject: Re: [Pharo-users] Pharo 2.0 and ODBC
You're joking, right?
I mean, if this is a way of helping me understand code by &q
You're joking, right?
I mean, if this is a way of helping me understand code by "commenting
it", I'd simply say Thanks, but no thanks!
If that's the way it's done in Smalltalk, I wonder where I have been the
last 17 years. I haven't done this and I can't remember seeing this. And
I've read a
On 24 June 2013 12:21, jtuc...@objektfabrik.de wrote:
> false ifTrue:
> [ self
> sqlSetEnvAttr: 200
> value: 2"SQL_ATTR_ODBC_VERSION" ].
>
> what does this false ifTrue: thing mean here?
>
That's how you comment code in Smalltalk - becuase it doesn't support
ne
Hi Friedrich,
I guess what could help people understand more about what the actual
differences might be is if you can exactly say under which Pharo version
and on which VM your ODBC connection had been working before. Was it
also on a 64 bit lInux? Even the same installation or some other 64 b
On 24 Jun 2013, at 15:50, Friedrich Dominicus
wrote:
> Sven Van Caekenberghe writes:
>
>> Hi Friedrich,
>>
>> On 24 Jun 2013, at 11:50, Friedrich Dominicus
>> wrote:
>>
>>> I have had this connection via ODBC running on Linux before. So I
>>> guess you are right with some libraries, but th
Sven Van Caekenberghe writes:
> Hi Friedrich,
>
> On 24 Jun 2013, at 11:50, Friedrich Dominicus
> wrote:
>
>> I have had this connection via ODBC running on Linux before. So I
>> guess you are right with some libraries, but they seem not to be related
>> to libpam.
>
> Have you tried using ldd t
Hi Friedrich,
sorry it didn't help. I just took a look at ODBCConnection and I see
that it uses ODBC 2 per default. (no similar logic to VA Smalltalk's
ODBC version determination and no call of SQLAllocHandle). So I guess I
cannot really help you any further.
Still there is some smell in ODB
Hi Friedrich,
On 24 Jun 2013, at 11:50, Friedrich Dominicus
wrote:
> I have had this connection via ODBC running on Linux before. So I
> guess you are right with some libraries, but they seem not to be related
> to libpam.
Have you tried using ldd to find dependencies (libs used by the vm or i
"jtuc...@objektfabrik.de" writes:
> Hi Friedrich,
>
> I am not sure if this is relevant for your case, but I had a very
> similar problem with VAST and DB2 on Linux 64 bits. The funny thing is
> that I also hat problems with the very same call and on digging deeper
> found out the problem is a mi
Hi Friedrich,
I am not sure if this is relevant for your case, but I had a very
similar problem with VAST and DB2 on Linux 64 bits. The funny thing is
that I also hat problems with the very same call and on digging deeper
found out the problem is a missing Ubuntu package. AFAIK, Pharo is also
Can anyone tell me if you got that combination running on a Linux 64-bit
box?
If'm trying to connect to the ODBC datasource I got:
pharo VM version: 3.9-7 #1 Wed Mar 13 18:22:44 CET 2013 gcc 4.4.3
Built from: NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid:
a53445f9-c0c0-4015-97a3-
19 matches
Mail list logo
