Hi Arron
Did you try Garage from https://github.com/pharo-rdbms
Stef
On Fri, Apr 20, 2018 at 7:22 AM, Aaron Blakeman
wrote:
> Hello,
>
> I'm trying to use Pharo 6 to connect to an Oracle 11g database. I tried
> using dbxtalk with the opendbx driver, but I can't seem to get that to load
> clean
Hello,
I'm trying to use Pharo 6 to connect to an Oracle 11g database. I tried
using dbxtalk with the opendbx driver, but I can't seem to get that to load
cleanly into a Pharo 6 image.
Before I spend alot of time trying to debug DBXtalk I wanted to see if
anyone else had any recommendations. Is
Hi,
On this matter, when I named my project, "Grafoscopio" I thought in
something evocative and unique, because of the Spanish words "grafo"
(graph) and grafía[1][2] (graphy, related with writing like in
"ortografía" "orthography". After naming it I discover there was a old
device related with wri
Perfect..
works for me..
Thanks!
On April 19, 2018 at 2:42:08 PM, Bernardo Ezequiel Contreras
(vonbecm...@gmail.com) wrote:
World>>System>>Settings>>Tools>>Software Configuration Management>>Iceberg
and choose the
File format type: tonel/filetree
peace,
sergio
photographer, journalist
you can avoid it if you go to
World>>System>>Settings>>Tools>>Software Configuration Management>>Iceberg
and choose the
File format type: tonel/filetree
On Thu, Apr 19, 2018 at 3:33 PM, Bernardo Ezequiel Contreras <
vonbecm...@gmail.com> wrote:
> see
> https://github.com/pharo-vcs/iceberg/issue
see
https://github.com/pharo-vcs/iceberg/issues/579
On Thu, Apr 19, 2018 at 1:04 PM, sergio ruiz wrote:
> I am just getting started with Iceberg.
>
> In creating a new repo on my local machine, I keep getting this error:
>
> Object>>doesNotUnderstand: #asSymbol
>
> it has a beef with this line
I am just getting started with Iceberg.
In creating a new repo on my local machine, I keep getting this error:
Object>>doesNotUnderstand: #asSymbol
it has a beef with this line:
defaultFileFormat
^ Smalltalk at: self defaultFileFormatType asSymbol
Do i need to set this in my image?
Th
This is tomorrow.
> On 13 Apr 2018, at 14:32, Marcus Denker wrote:
>
> Pharo Sprint Apr 20
>
> https://association.pharo.org/event-2789579
>
> We will organize a Pharo sprint / Moose dojo Apr 20 , starting at
> 10:00am. (Local Time Paris).
>
> Goals of this sprint:
>
> • Ph
The good news is that the same version of Pharo Launcher worked essentially
perfectly under Windows 10.
As expected, the launcher was installed in AppData\Local.
However, I continue to find an AppData\Roaming\pharo directory created when
the launcher was installed. Its contents are as I described
Thank you very much
2018-04-19 3:34 GMT-03:00 Esteban Lorenzano :
> Hi again,
>
> well, the problem is that 64bit images are translated from a 32bit version
> and some particular dictionaries need to be rehashed.
>
> 1073741904 is a long integer in 32bit and a small integer in 64bit ;)
>
> If you
A C long is guaranteed to be at least 32 bits in size.
long long is guaranteed to be 64 bits.
int depends on the platform.
Phil
On Thu, Apr 19, 2018 at 10:30 AM, Andres Valloud <
avall...@smalltalk.comcastbiz.net> wrote:
> The relevant spec does not state 'long' is of any particular size.
>
>
On Thu, Apr 19, 2018 at 10:32 AM, Thierry Goubier wrote:
>
>
> 2018-04-19 10:24 GMT+02:00 Serge Stinckwich :
>
>>
>>
>> On Thu, Apr 19, 2018 at 9:13 AM, Serge Stinckwich <
>> serge.stinckw...@gmail.com> wrote:
>>
>>> I try to understand differences between 32 bits and 64 bits FFI support
>>> for
On Thu, Apr 19, 2018 at 9:30 AM, Andres Valloud <
avall...@smalltalk.comcastbiz.net> wrote:
> The relevant spec does not state 'long' is of any particular size.
>
>
yes I know this is why we have also a platformLongAt: method.
I was just wondering, why we have a signedLongAt: method that return
signed long is now specified as:
Capable of containing at least the [−2,147,483,647, +2,147,483,647] range;
so at least 32 bits;
and signed long long
Capable of containing at least the [−9,223,372,036,854,775,807,
+9,223,372,036,854,775,807] range [C99]
so at least 64 bits;
and long long siz
2018-04-19 10:24 GMT+02:00 Serge Stinckwich :
>
>
> On Thu, Apr 19, 2018 at 9:13 AM, Serge Stinckwich <
> serge.stinckw...@gmail.com> wrote:
>
>> I try to understand differences between 32 bits and 64 bits FFI support
>> for C structures.
>>
>> I build a class called MyStruct subclass of FFIExtern
The relevant spec does not state 'long' is of any particular size.
On 4/19/18 1:24 , Serge Stinckwich wrote:
On Thu, Apr 19, 2018 at 9:13 AM, Serge Stinckwich
mailto:serge.stinckw...@gmail.com>> wrote:
I try to understand differences between 32 bits and 64 bits FFI
support for C struc
On Thu, Apr 19, 2018 at 9:13 AM, Serge Stinckwich <
serge.stinckw...@gmail.com> wrote:
> I try to understand differences between 32 bits and 64 bits FFI support
> for C structures.
>
> I build a class called MyStruct subclass of FFIExternalStructure.
> and define a layout for this structure like t
I try to understand differences between 32 bits and 64 bits FFI support for
C structures.
I build a class called MyStruct subclass of FFIExternalStructure.
and define a layout for this structure like this one :
MyStruct class>>fieldsDesc
"self rebuildFieldAccessors"
^ #(
int inde
18 matches
Mail list logo